From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: openembedded-core@lists.openembedded.org
Cc: xe-linux-external@cisco.com
Subject: [OE-core][PATCH] avahi: correct CVE_PRODUCT mapping
Date: Mon, 24 Aug 2026 04:01:56 -0700 [thread overview]
Message-ID: <20260824110156.25632-1-devanshp@cisco.com> (raw)
From: Devansh Patel <devanshp@cisco.com>
The current "avahi" mapping generates a vendor-wildcard product identity
for the packaged Avahi source.
Use "avahi:avahi", which matches the active NVD dictionary CPE, NVD
configuration criteria, and CNA affected data for the upstream project.
This changes the generated identity from
cpe:2.3:*:*:avahi:0.9~rc5:*:*:*:*:*:*:* to
cpe:2.3:*:avahi:avahi:0.9~rc5:*:*:*:*:*:*:*, but sbom-cve-check 1.3.3
with the frozen 2026-08-10 databases has no current CVE report delta.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
meta/recipes-connectivity/avahi/avahi_0.9.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-connectivity/avahi/avahi_0.9.bb b/meta/recipes-connectivity/avahi/avahi_0.9.bb
index 7cf0eb2b71..9397baa6ab 100644
--- a/meta/recipes-connectivity/avahi/avahi_0.9.bb
+++ b/meta/recipes-connectivity/avahi/avahi_0.9.bb
@@ -29,6 +29,8 @@ SRC_URI = "git://github.com/avahi/avahi;protocol=https;branch=master;tag=v0.9-rc
PV = "0.9~rc5"
SRCREV = "71b640e686964efb27cb708f4457ffaed183c319"
+CVE_PRODUCT = "avahi:avahi"
+
GITHUB_BASE_URI = "https://github.com/avahi/avahi/releases/"
CVE_STATUS[CVE-2021-26720] = "not-applicable-platform: Issue only affects Debian/SUSE"
--
2.35.6
next reply other threads:[~2026-08-24 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 11:01 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
2026-08-26 9:14 ` [OE-core][PATCH] avahi: correct CVE_PRODUCT mapping 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=20260824110156.25632-1-devanshp@cisco.com \
--to=devanshp@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xe-linux-external@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 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.