Skip to contentSkip to conversation

python3-flask-user: correct CVE_PRODUCT mapping

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

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 python3-flask-user: correct CVE_PRODUCT mapping

From: Devansh Patel <[email protected]>

The current "flask-user" mapping emits the wildcard-vendor *:flask-user CPE instead of the exact NVD identity for the packaged lingthio/Flask-User source.

Use "flask-user_project:flask-user", which is both an NVD dictionary CPE and an NVD configuration identity. CNA affected data uses "n/a:Flask-User" and remains covered by scanner aliases. With sbom-cve-check 1.3.3 and the pinned 2026-08-12 data, the generated identity changes but CVE-2021-23401 remains reported as affected.

---
 .../recipes-devtools/python/python3-flask-user_0.6.19.bb        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-python/recipes-devtools/python/python3-flask-user_0.6.19.bb +1 -1
index 68d7361519..c05c74b5c4 100644
@@ -11,7 +11,7 @@ SRC_URI[sha256sum] = "601abcc0343dfbae0c56273d98362d5cdc266ac84d20b3f65a212e4a2c
 PYPI_PACKAGE = "Flask-User"
 UPSTREAM_CHECK_PYPI_PACKAGE = "${PYPI_PACKAGE}"
 
-CVE_PRODUCT = "flask-user"
+CVE_PRODUCT = "flask-user_project:flask-user"
 
 inherit pypi setuptools3
 
Signature · 1 line
2.35.6