From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/3] package/ogre: add CPE
Date: Tue, 14 Jul 2026 11:38:45 +0200 [thread overview]
Message-ID: <ab13d9259139130265c3f5dd4823afe1@free.fr> (raw)
In-Reply-To: <20260706100301.60854-1-thomas.perale@mind.be>
On 06/07/2026 12:02, Thomas Perale via buildroot wrote:
> Vulnerabilities such as [1][2] are assigned to the ogre package with
> the
> cpe: ogre3d:ogre.
>
> To correctly match against those vulnerabilities the CPE_ID_VERSION
> uses
> the version without the 'v' prepended.
>
> [1] https://nvd.nist.gov/vuln/detail/CVE-2025-11014
> [2] https://nvd.nist.gov/vuln/detail/CVE-2025-11017
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-14 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 10:02 [Buildroot] [PATCH 1/3] package/ogre: add CPE Thomas Perale via buildroot
2026-07-06 10:03 ` [Buildroot] [PATCH 2/3] package/open62541: fix CPE_ID_VERSION Thomas Perale via buildroot
2026-07-17 15:47 ` Thomas Perale via buildroot
2026-07-06 10:03 ` [Buildroot] [PATCH 3/3] package/python-web2py: " Thomas Perale via buildroot
2026-07-17 15:47 ` Thomas Perale via buildroot
2026-07-14 9:38 ` Julien Olivain via buildroot [this message]
2026-07-17 15:47 ` [Buildroot] [PATCH 1/3] package/ogre: add CPE Thomas Perale via buildroot
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=ab13d9259139130265c3f5dd4823afe1@free.fr \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.perale@mind.be \
/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