Skip to contentSkip to conversation

python3-pyyaml: set CVE_PRODUCT

PATCH New Himanshu Jadon -X (hjadon - E INFOCHIPS PRIVATE LIMITED at Cisco) 1 participant 1 message Jul 29

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 python3-pyyaml: set CVE_PRODUCT

From: "mark.yang" <[email protected]>

The pypi class default python:pyyaml vendor prefix matches nothing, so PyYAML CVEs are not evaluated at all. The databases use two vendor spellings: pyyaml in the NVD CPEs, and "Red Hat" (with a space, not expressible as a vendor:product pair) in CVE-2020-1747's CNA record. Use the bare product name to cover both.

All four existing CVEs (CVE-2017-18342, CVE-2019-20477, CVE-2020-1747, CVE-2020-14343) are fixed by 5.4, so they resolve as not affected at 6.0.1.

Note: Original commit was for python3-pyyaml_6.0.3.bb. This is adjusted for scarthgap where recipe version is python3-pyyaml_6.0.1.bb.

(cherry picked from commit 89a0ba3c2da2a7755bafb28afbf75dc7112e2549)
---
 meta/recipes-devtools/python/python3-pyyaml_6.0.1.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-devtools/python/python3-pyyaml_6.0.1.bb +2 -0
index 3388312557..07bf851fce 100644
@@ -7,6 +7,8 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=6d8242660a8371add5fe547adf083079"
 
 PYPI_PACKAGE = "PyYAML"
 
+CVE_PRODUCT = "pyyaml"
+
 inherit pypi python_setuptools_build_meta
 
 SRC_URI += "file://0001-Fix-builds-with-Cython-3.patch"
Signature · 1 line
2.35.6