From: Paul Barker <paul@pbarker.dev>
To: hjadon@cisco.com, openembedded-core@lists.openembedded.org
Cc: vchavda@cisco.com
Subject: Re: [OE-core] [master] [PATCH] apt: Add CVE_PRODUCT to support product name
Date: Tue, 21 Apr 2026 12:45:44 +0100 [thread overview]
Message-ID: <b6875fed11ec10d190215ff3587a9553362a55a2.camel@pbarker.dev> (raw)
In-Reply-To: <20260421111028.2501890-1-hjadon@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
On Tue, 2026-04-21 at 04:10 -0700, Himanshu Jadon -X (hjadon - E
INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> 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"
CVE-2020-3810 [1] appears to have CPE "debian:apt" but not
"debian:advanced_package_tool", so I don't think we should exclude the
older CPE here.
[1]: https://nvd.nist.gov/vuln/detail/CVE-2020-3810
What is the goal of this patch and other patches from Cisco which set
CVE_PRODUCT? In most cases there don't seem to be any false positives
that you're trying to resolve, so I'm still unsure why CVE_PRODUCT needs
to be set in so many recipes.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-04-21 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 11:10 [OE-core] [master] [PATCH] apt: Add CVE_PRODUCT to support product name Himanshu Jadon -X (hjadon - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-21 11:45 ` Paul Barker [this message]
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=b6875fed11ec10d190215ff3587a9553362a55a2.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=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