From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/apache: ignore various CVEs
Date: Mon, 1 Aug 2022 20:57:28 +0200 [thread overview]
Message-ID: <20220801205728.51ac113f@windsurf> (raw)
In-Reply-To: <eb4cf15f-6e4d-43ca-f34d-a391044f430e@t-online.de>
Hello,
On Mon, 1 Aug 2022 20:05:23 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> my understanding of the CVE/CPE stuff is rather limited but I guess
> these CPEs show up for us because the database entry does not contain
> any version number:
>
> cpe:2.3:a:apache:http_server:-:*:*:*:*:*:*:*
>
> What about ignoring such version-less entries in buildroot?
No, this cannot work: at the time a CVE is added, it is sometimes not
known in which version the issue is fixed... because the fix may not
yet be in a stable release. So it is probably quite common to see a CPE
ID with "*" as the version, until the issue is fixed in an official
release of the project.
So ignoring version-less entries is really not a good idea, as we could
really miss a lot of real security problems.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-01 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 11:12 [Buildroot] [PATCH 1/1] package/apache: ignore various CVEs Bernd Kuhls
2022-08-01 17:56 ` Arnout Vandecappelle
[not found] ` <31fb8cf8-02e4-8bc6-a7b9-c6f9cd0845bc__49535.9333044448$1659376652$gmane$org@mind.be>
2022-08-01 18:05 ` Bernd Kuhls
2022-08-01 18:16 ` Arnout Vandecappelle
[not found] ` <eb4cf15f-6e4d-43ca-f34d-a391044f430e@t-online.de>
2022-08-01 18:55 ` Thomas Petazzoni via buildroot
2022-08-01 18:57 ` Thomas Petazzoni via buildroot [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=20220801205728.51ac113f@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=thomas.petazzoni@bootlin.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