From: Paul Barker <paul@pbarker.dev>
To: antonin.godard@bootlin.com, openembedded-core@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [PATCH] sbom-cve-check-common: print warnings on unpatched CVEs
Date: Tue, 21 Apr 2026 12:08:43 +0100 [thread overview]
Message-ID: <9369197a4e7f2d032decc797406ecba201fe6799.camel@pbarker.dev> (raw)
In-Reply-To: <20260421-sbom-cve-check-warnings-v1-1-df7861a0a0bc@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 3454 bytes --]
On Tue, 2026-04-21 at 11:15 +0200, Antonin Godard via
lists.openembedded.org wrote:
> The now removed cve-check class used to print warnings when CVEs with
> status "Unpatched" were found. Add this feature to the
> sbom-cve-check class with the same default value (enabled).
>
> For now it only does so when the cvecheck report type is enabled. It may
> be possible to do the same for the SPDX report type.
>
> Sample output:
>
> WARNING: core-image-minimal-1.0-r0 do_sbom_cve_check: busybox-1.37.0: Found unpatched CVEs: CVE-2024-58251
> WARNING: core-image-minimal-1.0-r0 do_sbom_cve_check: expat-2.7.5: Found unpatched CVEs: CVE-2025-66382, CVE-2026-41080
> WARNING: core-image-minimal-1.0-r0 do_sbom_cve_check: glibc-2.43+git: Found unpatched CVEs: CVE-2010-4756, CVE-2026-4046
>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> meta/classes/sbom-cve-check-common.bbclass | 31 ++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/meta/classes/sbom-cve-check-common.bbclass b/meta/classes/sbom-cve-check-common.bbclass
> index 6963ad71c61..d84416c8a50 100644
> --- a/meta/classes/sbom-cve-check-common.bbclass
> +++ b/meta/classes/sbom-cve-check-common.bbclass
> @@ -48,6 +48,33 @@ SBOM_CVE_CHECK_UPDATE_DB_DEPENDENCIES ?= " \
> sbom-cve-check-update-nvd-native:do_patch \
> "
>
> +SBOM_CVE_CHECK_SHOW_WARNINGS ?= "1"
> +SBOM_CVE_CHECK_SHOW_WARNINGS[doc] = "Show warning messages when unpatched CVEs are found. \
> +Requires the SBOM_CVE_CHECK_EXPORT_CVECHECK report type to be enabled"
> +
> +def show_warnings_from_file(cvecheck_export_file):
> + import json
> + report = {}
We shouldn't need to initialise report here as it is always set if we
get past the try block below.
> +
> + try:
> + with open(cvecheck_export_file, "r") as f:
> + report = json.load(f)
> + except (json.JSONDecodeError, UnicodeDecodeError) as e:
> + bb.error(f"Failed to open JSON report file {f}: {e}")
> + return
> +
> + packages = report.get("package", [])
> + for package in packages:
> + unpatched = []
> + cves = package.get("issue", [])
> + for cve in cves:
> + if cve["status"] == "Unpatched":
> + unpatched.append(cve["id"])
> + if unpatched:
> + pname = package["name"]
> + version = package["version"]
> + bb.warn(f"{pname}-{version}: Found unpatched CVEs: {', '.join(unpatched)}")
> +
> def run_sbom_cve_check(d, sbom_path, export_base_name, export_link_name=None):
> import os
> import bb
> @@ -94,9 +121,13 @@ def run_sbom_cve_check(d, sbom_path, export_base_name, export_link_name=None):
> bb.error(f"sbom-cve-check failed: {e}")
> return
>
> + show_warnings = oe.utils.vartrue("SBOM_CVE_CHECK_SHOW_WARNINGS", True, False, d)
I think this can be:
show_warnings = bb.utils.to_boolean(d.getVar("SBOM_CVE_CHECK_SHOW_WARNINGS"))
> +
> for export_type, export_file, export_link in export_files:
> bb.note(f"sbom-cve-check exported: {export_file}")
> if export_link:
> update_symlinks(export_file, export_link)
> + if show_warnings and export_type == d.getVarFlag("SBOM_CVE_CHECK_EXPORT_CVECHECK", "type"):
> + show_warnings_from_file(export_file)
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-04-21 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 9:15 [PATCH] sbom-cve-check-common: print warnings on unpatched CVEs Antonin Godard
2026-04-21 11:08 ` Paul Barker [this message]
2026-04-21 12:44 ` [OE-core] " Antonin Godard
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=9369197a4e7f2d032decc797406ecba201fe6799.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.com \
/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