From: Benjamin Robin <benjamin.robin@bootlin.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Ross Burton <ross.burton@arm.com>
Subject: Re: [PATCH 6/6] mpg123: set status for CVE-2006-3355
Date: Tue, 14 Apr 2026 08:44:26 +0200 [thread overview]
Message-ID: <7931127.EvYhyI6sBW@brobin-bootlin> (raw)
In-Reply-To: <AS1PR10MB5697198A4211439AC1A131A8FD242@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Monday, April 13, 2026 at 11:23 PM, Marko, Peter wrote:
> Benjamin,
>
> This one is weird
> How can someone debug the sbom-cve-check script to figure out why the match is positive or negative?
> That would be great feature if there would be some option to print the comparisons.
Yeah, this is in the backlog, sbom-cve-check should have an "audit log".
But this is not that simple, and I have other priorities :)
> Peter
> > From: Peter Marko <peter.marko@siemens.com>
> >
> > This seems to be a bug in sbom-cve-check.
> > I could get a clean report with following fkie change:
> >
> > "cpeMatch": [
> > + {
> > + "vulnerable": true,
> > + "criteria": "cpe:2.3:a:mpg123:mpg123:0.59r:*:*:*:*:*:*:*",
> > + "matchCriteriaId": "1F8EEF7E-C6BB-4669-81D2-68AABF8A7686"
> > + },
> > {
> > "vulnerable": true,
> > "criteria": "cpe:2.3:a:mpg123:mpg123:pre0.59s_r11:*:*:*:*:*:*:*",
> > "matchCriteriaId": "9765C6AD-E1F0-421C-B7B1-C09AD83A3DB7"
> > }
> > ]
The algorithm is described here:
https://sbom-cve-check.readthedocs.io/en/latest/design.html#compute-vex-assessment
But in summary, the CVE is found "applicable" (associated with mpg123 component),
but no valide version range was found (pre0.59s_r11 is not a valid version).
So as documented: "In the end if no assessment could be computed, generate a
default assessment indicating that databases do not contain enough version
information. This default assessment considers that the component is affected
(vulnerable) by this CVE".
> >
> > However I'm not sure why adding another vulnerable version should switch
> > the vulnerability flag from true to false...
Adding a new valid cpeMatch entry is going to fix it. But maybe not exactly
this one, I guess we need to express that version range <= 0.59
For information, I am currently working on a big improvement for the
generation of VEX assessment (statement and status notes).
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-04-14 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 21:14 [PATCH 1/6] xdg-utils: set status for CVE-2025-52968 Peter Marko
2026-04-13 21:14 ` [PATCH 2/6] wic: set CVE_PRODUCT Peter Marko
2026-04-13 21:14 ` [PATCH 3/6] tar: set status for CVE-2025-45582 Peter Marko
2026-04-13 21:14 ` [PATCH 4/6] screen: set status for CVE-2025-46802 Peter Marko
2026-04-13 21:14 ` [PATCH 5/6] ovmf: set status for CVE-2024-1298 Peter Marko
2026-04-13 21:14 ` [PATCH 6/6] mpg123: set status for CVE-2006-3355 Peter Marko
2026-04-13 21:23 ` Marko, Peter
2026-04-14 6:44 ` Benjamin Robin [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=7931127.EvYhyI6sBW@brobin-bootlin \
--to=benjamin.robin@bootlin.com \
--cc=Peter.Marko@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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