From: "Himanshu Jadon -X (hjadon - E INFOCHIPS PRIVATE LIMITED at Cisco)" <hjadon@cisco.com>
To: openembedded-core@lists.openembedded.org
Cc: vchavda@cisco.com
Subject: [OE-core] [master] [PATCH] apt: Add CVE_PRODUCT to support product name
Date: Tue, 21 Apr 2026 04:10:28 -0700 [thread overview]
Message-ID: <20260421111028.2501890-1-hjadon@cisco.com> (raw)
From: Himanshu Jadon <hjadon@cisco.com>
- NVD contains older debian:apt CPEs, but they are deprecated and
explicitly replaced by debian:advanced_package_tool, so the recipe
should use the active normalized product identity.
- Therefore, set CVE_PRODUCT to align with the NVD CPE and ensure
correct CVE reporting.
Signed-off-by: Himanshu Jadon <hjadon@cisco.com>
---
meta/recipes-devtools/apt/apt_3.0.3.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-devtools/apt/apt_3.0.3.bb b/meta/recipes-devtools/apt/apt_3.0.3.bb
index d2dfe48e9a..871564baea 100644
--- a/meta/recipes-devtools/apt/apt_3.0.3.bb
+++ b/meta/recipes-devtools/apt/apt_3.0.3.bb
@@ -148,3 +148,6 @@ do_install:append() {
# Avoid non-reproducible -src package
sed -i -e "s,${B}/include/,,g" ${B}/apt-pkg/tagfile-keys.cc
}
+
+# Add CVE_PRODUCT to match the NVD CPE product name
+CVE_PRODUCT = "debian:advanced_package_tool"
--
2.35.6
next reply other threads:[~2026-04-21 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 11:10 Himanshu Jadon -X (hjadon - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
2026-04-21 11:45 ` [OE-core] [master] [PATCH] apt: Add CVE_PRODUCT to support product name Paul Barker
2026-04-21 14:04 ` Himanshu Jadon -X (hjadon - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-22 10:31 ` [OE-core] " Paul Barker
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=20260421111028.2501890-1-hjadon@cisco.com \
--to=hjadon@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=vchavda@cisco.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox