From: Grant.Smith3@ngc.com
To: poky@lists.yoctoproject.org
Subject: CVE CHECK scorev3
Date: Wed, 11 Oct 2023 17:19:12 -0700 [thread overview]
Message-ID: <DxsL.1697069952825184652.wun3@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
All,
In the poky layer (yocto-4.2.3 branch) I am using the built in cve-checker and running into an issue where it is unable to produce the scorev3 metric. All CVEs have a scorev3 equivalent to 0.0. When looking at poky (yocto-4.0.9 branch) I noticed that the cve-checker uses the 1.1 version of the NVD database and can successfully produce scorev3 when running a test build. The yocto-4.2.3 branch uses version 2 of the database. There have also been several patches that affect the way these scores are produced. I am just wondering if anyone might have any insight to this issue or maybe have a solution.
Thanks
[-- Attachment #2: Type: text/html, Size: 696 bytes --]
next reply other threads:[~2023-10-12 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 0:19 Grant.Smith3 [this message]
2023-10-13 13:19 ` [poky] CVE CHECK scorev3 Ross Burton
2023-10-13 13:52 ` Smith, Grant [US] (MS)
2023-10-13 14:23 ` Steve Sakoman
2023-10-14 8:33 ` Marta Rybczynska
2023-10-14 14:49 ` EXT :Re: " Smith, Grant [US] (MS)
[not found] ` <178DEC4DABB5202F.14388@lists.yoctoproject.org>
2023-10-17 9:14 ` Marta Rybczynska
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=DxsL.1697069952825184652.wun3@lists.yoctoproject.org \
--to=grant.smith3@ngc.com \
--cc=poky@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 read-only IMAP folder(s) and NNTP newsgroup(s).