Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 24 Jun 2019 18:27:30 +0200
From: Alexander Potapenko <>
Subject: Re: Thousands of vulnerabilities, almost no CVEs: OSS-Fuzz

On Mon, Jun 24, 2019 at 5:44 PM Bob Friesenhahn
<> wrote:
> On Mon, 24 Jun 2019, Dmitry Vyukov wrote:
> >
> > So what are community thoughts on automatic CVE assignment?
> > That would definitely get some attention to these bugs by vendors
> > (because that's open CVEs in their products then). And this should be
> > implementable because both OSS-Fuzz and syzbot are automated enough
> > already. However I afraid that these CVEs may be as automatically
> > sorted into a trashcan then :)
> An excess of CVEs would cause CVEs to be not very meaningful any more.
> Most oss-fuzz issue detections are not CVE worthy.  For example, a
> one-byte read "heap overflow" is not likely to cause any actual harm
> but oss-fuzz would classify it as "heap overflow".
There's enough information in the report though to assign the severity
score depending on the access size, its type (read or write) the call
stack etc.
OSS-Fuzz deliberately doesn't do that now, but such scoring can be
done to prune the list of potential CVE candidates.
> Bob
> --
> Bob Friesenhahn
> GraphicsMagick Maintainer,
> Public Key,

Alexander Potapenko
Software Engineer

Google Germany GmbH
Erika-Mann-Straße, 33
80636 München

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg

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.