Skip to contentSkip to conversation

python3-m2crypto: correct CVE_PRODUCT mapping

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

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 python3-m2crypto: correct CVE_PRODUCT mapping

From: Devansh Patel <[email protected]>

The current product-only "m2crypto" mapping generates a wildcard-vendor identity instead of the two vendors used for the packaged source.

Use "heikkitoivonen:m2crypto" and "m2crypto_project:m2crypto" for their exact NVD dictionary CPE and NVD configuration identities. This changes the generated CPE set, but sbom-cve-check 1.3.3 with the pinned NVD snapshot has no current CVE report delta.

---
 meta-python/recipes-devtools/python/python3-m2crypto_0.49.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-python/recipes-devtools/python/python3-m2crypto_0.49.0.bb +1 -1
index b9e872fe67..98db2eceb1 100644
@@ -53,6 +53,6 @@ do_install:append() {
     rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/M2Crypto/__pycache__/*.cpython-*.pyc
 }
 
-CVE_PRODUCT = "m2crypto"
+CVE_PRODUCT = "heikkitoivonen:m2crypto m2crypto_project:m2crypto"
 
 BBCLASSEXTEND = "native"
Signature · 1 line
2.35.6