From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 4/5] support/scripts/cve-check: fix vulnerabilities with different analysis
Date: Fri, 29 May 2026 17:39:34 +0200 [thread overview]
Message-ID: <ahmzJzMLwCMwxmMB@windsurf> (raw)
In-Reply-To: <20260529150631.447940-4-thomas.perale@mind.be>
On Fri, May 29, 2026 at 05:06:30PM +0200, Thomas Perale via buildroot wrote:
> Before this commit, only one entry per vulnerability ID was added to the
> output. In CycloneDX, if you need to provide different analyses for
> different affected components with the same vulnerability ID, you must
> create multiple entries with the same ID.
>
> When running `cve-check` with the `--include-resolved` argument, the
> analysis of some vulnerabilities would get overwritten, which led to
> undefined analysis results.
>
> This is especially true when running the analysis on multiple components
> with the same name but different versions. For instance, if the input
> SBOM includes both the `gnupg` and `gnupg2` packages, CVE-2025-68973
> could be included. This CVE might be exploitable for the `gnupg` package
> but resolved for `gnupg2`. Therefore, a single analysis entry cannot
> cover both cases.
>
> This commit fixes the logic for adding vulnerabilities to the output
> SBOM. A vulnerability is now added as a new entry if:
>
> 1. A vulnerability with the same ID doesn't exist yet.
> 2. The affect of the new vulnerability is not the same as the one
> already present.
>
> For the CVE-2025-68973 example this would result in the following
> output:
>
> ```json
> [
> {
> "id": "CVE-2025-68973",
> "analysis": {
> "state": "exploitable"
> }
> "affects": [
> {"ref": "gnupg"}
> ]
> },
> {
> "id": "CVE-2025-68973",
> "analysis": {
> "state": "resolved"
> }
> "affects": [
> {"ref": "gnupg2"}
> ]
> }
> ]
> ```
>
> 45 vulnerabilities were concerned by this bug over the Buildroot tree.
>
> Co-Authored-By: Tim Soubry <tim.soubry@mind.be>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to master, thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-29 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:06 [Buildroot] [PATCH v2 1/5] support/scripts/cve-check: fix vulnerability timestamp to RFC 3339 Thomas Perale via buildroot
2026-05-29 15:06 ` [Buildroot] [PATCH v2 2/5] support/scripts/cve-check: add indication how to run Thomas Perale via buildroot
2026-05-29 15:36 ` Thomas Petazzoni via buildroot
2026-06-05 12:51 ` Thomas Perale via buildroot
2026-05-29 15:06 ` [Buildroot] [PATCH v2 3/5] support/scripts/cve-check: remove 'bom-ref' for vulnerabilities Thomas Perale via buildroot
2026-05-29 15:39 ` Thomas Petazzoni via buildroot
2026-05-29 15:06 ` [Buildroot] [PATCH v2 4/5] support/scripts/cve-check: fix vulnerabilities with different analysis Thomas Perale via buildroot
2026-05-29 15:39 ` Thomas Petazzoni via buildroot [this message]
2026-06-05 12:51 ` Thomas Perale via buildroot
2026-05-29 15:06 ` [Buildroot] [PATCH v2 5/5] package/pkg-generic.mk: replicate IGNORE_CVES to host packages Thomas Perale via buildroot
2026-05-29 15:39 ` Thomas Petazzoni via buildroot
2026-06-05 12:51 ` Thomas Perale via buildroot
2026-05-29 15:33 ` [Buildroot] [PATCH v2 1/5] support/scripts/cve-check: fix vulnerability timestamp to RFC 3339 Thomas Petazzoni via buildroot
2026-06-05 12:51 ` Thomas Perale via buildroot
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=ahmzJzMLwCMwxmMB@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.