Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Apr 2015 18:02:32 +0000
From: mancha <>
Subject: Re: cve-assign delays

On Thu, Mar 19, 2015 at 03:18:33PM -0400, Steven M. Christey wrote:
> We recognize that some requesters have experienced delays, and
> sometimes lengthy delays, in getting CVE IDs assigned. We apologize
> for those delays.
> The number of cve-assign requests has been growing dramatically, as
> has the number of unique and new requesters. Our goal is always to
> provide reasonable response times, and we were caught by the spike in
> requests.
> We are working to improve our responsiveness through a combination of
> process changes, improved communications, and staffing shifts.
> We appreciate your understanding and expect that you will see positive
> changes in the cve-assign response times over the coming weeks.
> Best regards, Steve Christey Coley


I had been wondering about the delays so many thanks for your email.

What's not entirely clear to me is how you're dealing with the existing
backlog. Are reporters expected to re-submit requests?

For example, I have two outstanding requests from mid-February:

  1. glibc
  2. xrdp

Are those still on MITRE's radar screen? Thanks.


Content of type "application/pgp-signature" skipped

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.