[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bbba28f0-baf1-6eb5-3269-db3dc9c2b8ec@geeklan.co.uk>
Date: Wed, 14 Dec 2016 14:36:15 +0000
From: Sevan Janiyan <venture37@...klan.co.uk>
To: oss-security@...ts.openwall.com
Subject: Re: why many CVEs are ** RESERVED ** on Mitre
Hello,
On 14/12/2016 14:24, Kurt Seifried wrote:
> ** RESERVED ** This candidate has been reserved by an organization
> or individual that will use it when announcing a new security problem.
> When the candidate has been publicized, the details for this
> candidate will be provided.
>
> This means that the entry number has been reserved by Mitre for an issue or
> a CNA has reserved the number. So in the case where a CNA requests a block
> of CVE numbers in advance (e.g. Red Hat currently requests CVEs in blocks
> of 500), the CVE number will be marked as reserved even though the CVE
> itself may not be assigned by the CNA for some time. Until the CVE is
> assigned AND Mitre is made aware of it (e.g. the embargo passes and the
> issue is made public), AND Mitre has researched the issue and written a
> description of it, entries will show up as "** RESERVED **".
This creates a situation where the Mitre site dose not provide any
information despite, marking the CVE as reserved despite an official
advisory for effected software referencing the CVE.
Somewhat frustrating when performing vulnerability management as the
mitre URL is self documenting but useless to reference as a source.
Sevan
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
