[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD77+gST6rs=eL5BehV_ffVHo0d6FezKM2Wx61Qy+G4Bg6eE2g@mail.gmail.com>
Date: Sun, 9 Aug 2020 10:26:44 +0200
From: Richard Hartmann <richih.mailinglist@...il.com>
To: Sylvain Beucler <beuc@...c.net>
Cc: oss-security@...ts.openwall.com, prometheus-team@...glegroups.com,
Prometheus Developers <prometheus-developers@...glegroups.com>
Subject: Re: Voiding CVE-2020-16248
Thanks, Sylvain & Florian.
I wasn't aware that MITRE offered this option. I didn't want to send
email to them as I could no be certain if they own the CVE and as
putting random support burden on a closed list is worse than putting
it onto an open list IMO.
Will do.
On Sat, Aug 8, 2020 at 12:41 PM Sylvain Beucler <beuc@...c.net> wrote:
>
> Hi,
>
> On 08/08/2020 10:49, Richard Hartmann wrote:
> > I could not find out which organization has
> > reserved CVE-2020-16248 so I decided to send email to this list to
> > inform the organization, enabling them to update their records.
>
> I would suggest reaching MITRE:
> https://cve.mitre.org/cve/update_cve_entries.html
> - "Request an update to an exiting CVE entry"
> - Type: "Rejection"
>
> They'll either do the update or point you to the assigning CNA.
>
> Most likely they'll mark the issue as "DISPUTED" within a few business days.
>
> Cheers!
> Sylvain
--
Richard
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.
