|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
upcoming intel issue
- To: cve-editorial-board-list <cve-editorial-board-list@lists.mitre.org>
- Subject: upcoming intel issue
- From: Kurt Seifried <kurt@seifried.org>
- Date: Wed, 3 Jan 2018 13:00:31 -0700
- Authentication-results: spf=none (sender IP is 198.49.146.235) smtp.mailfrom=LISTS.MITRE.ORG; imc.mitre.org; dkim=none (message not signed) header.d=none;imc.mitre.org; dmarc=none action=none header.from=seifried.org;
- Delivery-date: Wed Jan 3 15:04:51 2018
- List-help: <mailto:LISTSERV@LISTS.MITRE.ORG?body=INFO%20CVE-EDITORIAL-BOARD-LIST>
- List-owner: <mailto:CVE-EDITORIAL-BOARD-LIST-request@LISTS.MITRE.ORG>
- List-subscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-subscribe-request@LISTS.MITRE.ORG>
- List-unsubscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-unsubscribe-request@LISTS.MITRE.ORG>
- Sender: <owner-cve-editorial-board-list@lists.mitre.org>
- Spamdiagnosticmetadata: 5952c28dcc454f0789fb433d26f936ef
- Spamdiagnosticoutput: 1:2
So the thing that's in the news, assuming it has CVEs, can we make sure they are populated to the CVE database asap, and if Intel does not do we have a plan B (e.g. MITRE writes them up?).
Also in general I think we should probably figure out some guidelines for these high visibility issues, e.g. encourage the original CNA to get them into the database asap, and have a plan B in case they don't (e.g. MITRE or someone else with info writes them up? first come first served? trusted parties only? or?).
--
Kurt Seifried
kurt@seifried.org
kurt@seifried.org
- Follow-Ups:
- Re: upcoming intel issue
- From: "Landfield, Kent" <Kent_Landfield@McAfee.com>
- Re: upcoming intel issue
- From: Art Manion <amanion@cert.org>
- Re: upcoming intel issue
- Next by Date: Re: upcoming intel issue
- Next by thread: Re: upcoming intel issue
- Index(es):