From: ankur.tyagi85@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Devansh Patel <devanshp@cisco.com>,
Khem Raj <khem.raj@oss.qualcomm.com>,
Ankur Tyagi <ankur.tyagi85@gmail.com>
Subject: [oe][meta-python][wrynose][PATCH 13/20] python3-web3: add CVE_PRODUCT mapping
Date: Sun, 23 Aug 2026 23:51:51 +1200 [thread overview]
Message-ID: <20260823115158.1582363-13-ankur.tyagi85@gmail.com> (raw)
In-Reply-To: <20260823115158.1582363-1-ankur.tyagi85@gmail.com>
From: Devansh Patel <devanshp@cisco.com>
The current inherited "python:web3" mapping does not match the web3.py identities used by NVD and CVE List V5, so its source-aligned CVE is missed.
Use "ethereum:web3.py" for the CNA affected-data identity and "apeworx:web3.py" for the NVD dictionary CPE and configuration identity.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
(cherry picked from commit 19ecb40f50cb5c93eb2830b10c4a5b02e367e4e7)
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
meta-python/recipes-devtools/python/python3-web3_7.12.1.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-python/recipes-devtools/python/python3-web3_7.12.1.bb b/meta-python/recipes-devtools/python/python3-web3_7.12.1.bb
index fe5886692d..18fa1d8d1c 100644
--- a/meta-python/recipes-devtools/python/python3-web3_7.12.1.bb
+++ b/meta-python/recipes-devtools/python/python3-web3_7.12.1.bb
@@ -6,6 +6,8 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=1d34d9701a1461e4bd71a904ac4cf7be"
SRC_URI[sha256sum] = "97f6a116ccaeb5907bb4cb6c771cc23bc942bf09528a840189e9b509b7b8347c"
+CVE_PRODUCT = "ethereum:web3.py apeworx:web3.py"
+
inherit pypi setuptools3
RDEPENDS:${PN} += " \
next prev parent reply other threads:[~2026-08-23 11:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 11:51 [oe][meta-oe][wrynose][PATCH 1/20] thin-provisioning-tools: upgrade 1.3.1 -> 1.3.3 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 2/20] hiredis: upgrade 1.3.0 -> 1.3.1 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 3/20] libsdl3-image: upgrade 3.4.2 -> 3.4.4 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 4/20] libsdl3: upgrade 3.4.4 -> 3.4.8 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-networking][wrynose][PATCH 5/20] postfix: upgrade 3.10.12 -> 3.10.13 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-networking][wrynose][PATCH 6/20] firewalld: upgrade 2.2.1 -> 2.2.3 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 7/20] file-roller: upgrade 44.5 -> 44.7 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 8/20] gnome-software: upgrade 50.0 -> 50.3 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 9/20] gdm: upgrade 50.1 -> 50.2 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 10/20] gvfs: upgrade 1.60.0 -> 1.60.1 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-gnome][wrynose][PATCH 11/20] gvfs: upgrade 1.60.1 -> 1.60.2 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-python][wrynose][PATCH 12/20] python3-filelock: set CVE_PRODUCT ankur.tyagi85
2026-08-23 11:51 ` ankur.tyagi85 [this message]
2026-08-23 11:51 ` [oe][meta-python][wrynose][PATCH 14/20] python3-httplib2: correct CVE_PRODUCT mapping ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 15/20] python3-psycopg: upgrade 3.3.3 -> 3.3.4 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-oe][wrynose][PATCH 16/20] cjose: upgrade 0.6.2.7 -> 0.6.2.8 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-webserver][wrynose][PATCH 17/20] swagger-ui: upgrade 5.32.11 -> 5.32.12 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-webserver][wrynose][PATCH 18/20] swagger-ui: upgrade 5.32.12 -> 5.32.13 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-networking][wrynose][PATCH 19/20] samba: upgrade 4.23.8 -> 4.23.11 ankur.tyagi85
2026-08-23 11:51 ` [oe][meta-webserver][wrynose][PATCH 20/20] swagger-ui: upgrade 5.32.13 -> 5.32.14 ankur.tyagi85
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260823115158.1582363-13-ankur.tyagi85@gmail.com \
--to=ankur.tyagi85@gmail.com \
--cc=devanshp@cisco.com \
--cc=khem.raj@oss.qualcomm.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.