Skip to contentSkip to conversation

libxml2: correct CVE_PRODUCT mapping

PATCH New Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) 1 participant 1 message Aug 26

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libxml2: correct CVE_PRODUCT mapping

From: Devansh Patel <[email protected]>

The default product-only mapping generates a vendor-wildcard CPE. xmlsoft:libxml2 is the active NVD dictionary CPE and configuration identity, while gnome:libxml2 covers authoritative CNA affected data for the same GNOME source, including two records exclusive to that backend identity.

This changes the generated identities to two exact CPEs, but the frozen sbom-cve-check database leaves the 112-entry CVE report unchanged, with no current CVE delta.

---
 meta/recipes-core/libxml/libxml2_2.15.3.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-core/libxml/libxml2_2.15.3.bb +2 -0
index 8b0ba29412..7ddba7429c 100644
@@ -31,6 +31,8 @@ BINCONFIG = "${bindir}/xml2-config"
 
 inherit autotools pkgconfig binconfig-disabled ptest
 
+CVE_PRODUCT = "xmlsoft:libxml2 gnome:libxml2"
+
 # libxml2 publishes bugfix/security-only micro releases on its per-minor
 # release branches.
 inherit upstream-stable-release-point
Signature · 1 line
2.35.6