Skip to contentSkip to conversation

python3-py: 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-py: correct CVE_PRODUCT mapping

From: Devansh Patel <[email protected]>

The product-only "py" mapping generates a wildcard-vendor identity instead of the exact NVD identity for the packaged pytest-dev py source. Use "pytest:py" for its NVD dictionary CPE and configuration matches.

This changes the generated product identity. With sbom-cve-check 1.3.3, the current CVE report is unchanged using the pinned database snapshots; both mappings report CVE-2020-29651 and CVE-2022-42969.

---
 meta-python/recipes-devtools/python/python3-py_1.11.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-python/recipes-devtools/python/python3-py_1.11.0.bb +1 -1
index 61f3873b4c..76cb4ce745 100644
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=a6bb0320b04a0a503f12f69fea479de9"
 
 SRC_URI[sha256sum] = "51c75c4126074b472f746a24399ad32f6053d1b34b68d2fa41e558e6f4a98719"
 
-CVE_PRODUCT = "py"
+CVE_PRODUCT = "pytest:py"
 CVE_STATUS[CVE-2022-42969] = "disputed: upstream could not reproduce it, github also revoked the advisory"
 
 DEPENDS += "python3-setuptools-scm-native"
Signature · 1 line
2.35.6