From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <Anders.Montonen@iki.fi>
Cc: <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] cve-checker name collisions
Date: Mon, 27 Jan 2020 09:04:47 +0000 [thread overview]
Message-ID: <20200127090446.GY104502@korppu> (raw)
In-Reply-To: <A04CBFEE-A6E1-48BE-8F36-67F11D6886BD@iki.fi>
On Mon, Jan 27, 2020 at 10:16:16AM +0200, Anders Montonen wrote:
> On 24 Jan 2020, at 12:54, Ross Burton <ross.burton@intel.com> wrote:
> >
> > On 24/01/2020 09:02, Anders Montonen wrote:
> >> Hi,
> >> What's the best way for handling name collisions when using the cve-checker tool? For example, there's a ton of Adobe Flex vulnerabilities that are reported against the Flex lexical analyzer generator tool. Whitelisting the individual CVEs would be one option, but the list is pretty long.
> >
> > Set CVE_PRODUCT, if you use a colon then you can set the vendor too.
> >
> > This specific instance is already fixed in oe-core master:
> >
> > # Not Apache Flex, or Adobe Flex, or IBM Flex.
> > CVE_PRODUCT = "flex_project:flex”
>
> Thanks (and to Mikko too), that worked, though I’m a bit curious how one would find the proper vendor name, especially for a project like this where there’s no clear company name.
I always search for existing CVEs for the SW component and check what
project and product names were used.
For flex, Internet search shows for example
https://www.suse.com/security/cve/CVE-2019-6293/
which has "flex_project:flex" in NVD:
https://nvd.nist.gov/vuln/detail/CVE-2019-6293
In my projects I also have exported CVE_PRODUCT to buildhistory and
have a check for CVE product name. Any SW components with non-CLOSED
LICENSE must either have a matching CPE in NVD database or be checked
manually and whitelisted.
Cheers,
-Mikko
prev parent reply other threads:[~2020-01-27 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 9:02 cve-checker name collisions Anders Montonen
2020-01-24 9:41 ` [yocto] " Mikko Rapeli
2020-01-24 10:54 ` Ross Burton
2020-01-27 8:16 ` Anders Montonen
2020-01-27 9:04 ` Mikko Rapeli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200127090446.GY104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=Anders.Montonen@iki.fi \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).