From: Quentin Schulz <quentin.schulz@cherry.de>
To: ross.burton@arm.com, openembedded-core@lists.openembedded.org
Cc: Trevor Woerner <twoerner@gmail.com>
Subject: Re: [OE-core] [PATCH] wic: set CVE_PRODUCT
Date: Fri, 24 Apr 2026 12:30:46 +0200 [thread overview]
Message-ID: <e2f9fb8d-3026-4af7-a8af-94f2e6a8a583@cherry.de> (raw)
In-Reply-To: <20260413202233.2335301-1-ross.burton@arm.com>
Hi Ross,
On 4/13/26 10:22 PM, Ross Burton via lists.openembedded.org wrote:
> There are CVEs such as CVE-2008-6713 which have a CPE of *:wic, which
> get reported for our wic now that it has been split out to a standalone
> tool.
>
> Set CVE_PRODUCT to yoctoproject:wic to avoid this. There are no CVEs for
> wic yet, but this is the likely CPE that would be used.
>
Considering the many different CPEs I've found for well-known pieces of
software, I have a very low trust in "likely".
It'd be a good step forward to document in SECURITY.md in the wic repo
which CPE to use, to avoid having too many CPEs if security researchers
can read and follow instructions. However, it seems SECURITY.md isn't
available on all branches on wic and it for sure isn't on the master
branch, so no idea how we're supposed to do this. Adding Trevor in Cc.
Cheers,
Quentin
prev parent reply other threads:[~2026-04-24 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 20:22 [PATCH] wic: set CVE_PRODUCT Ross Burton
2026-04-24 10:30 ` Quentin Schulz [this message]
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=e2f9fb8d-3026-4af7-a8af-94f2e6a8a583@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=twoerner@gmail.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