From: Ross Burton <Ross.Burton@arm.com>
To: "hetpat@cisco.com" <hetpat@cisco.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v1] mpfr: Add vendor to CVE_PRODUCT to exclude false positives
Date: Tue, 3 Mar 2026 15:21:44 +0000 [thread overview]
Message-ID: <793AF32D-BD43-4405-8CF4-774696497399@arm.com> (raw)
In-Reply-To: <20260226125415.53196-2-hetpat@cisco.com>
On 26 Feb 2026, at 12:54, Het Patel via lists.openembedded.org <hetpat=cisco.com@lists.openembedded.org> wrote:
>
> From: Het Patel <hetpat@cisco.com>
>
> - Added the vendor to CVE_PRODUCT to prevent false positives.
What false positives? If this is actually “add the vendor because existing CVEs use this exact CPE” then say so, but please reassure us without having to do our own verification that this doesn’t actually mean we miss some CVEs.
Basically, changing the CVE_PRODUCT is good if it improves the detection, but changes should be backed up with evidence.
Ross
next prev parent reply other threads:[~2026-03-03 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:54 [OE-core] [PATCH v1] util-linux: Add vendor to CVE_PRODUCT to exclude false positives Het Patel -X (hetpat - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-02-26 12:54 ` [OE-core] [PATCH v1] mpfr: " Het Patel -X (hetpat - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-03 15:21 ` Ross Burton [this message]
2026-02-26 12:54 ` [OE-core] [PATCH v1] python3-dbus: Add CVE_PRODUCT to support product name Het Patel -X (hetpat - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-03 15:19 ` Ross Burton
2026-03-09 13:41 ` Het Patel -X (hetpat - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-02-26 13:17 ` [OE-core] [PATCH v1] util-linux: Add vendor to CVE_PRODUCT to exclude false positives Marko, Peter
2026-02-27 9:05 ` Het Patel -X (hetpat - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-02-27 9:10 ` Marko, Peter
2026-02-27 12:51 ` Het Patel -X (hetpat - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-02 8:19 ` Marko, Peter
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=793AF32D-BD43-4405-8CF4-774696497399@arm.com \
--to=ross.burton@arm.com \
--cc=hetpat@cisco.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox