From: Arnout Vandecappelle <arnout@mind.be>
To: Bernd Kuhls <bernd.kuhls@t-online.de>, buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/1] package/apache: ignore various CVEs
Date: Mon, 1 Aug 2022 20:16:24 +0200 [thread overview]
Message-ID: <6b20e25f-e562-d4aa-3da5-1000ab3f43bf@mind.be> (raw)
In-Reply-To: <pan$5b6cb$bb19d38$901acf5f$10cb6fe3@ID-313208.user.individual.net>
On 01/08/2022 20:05, Bernd Kuhls wrote:
> Hi Arnout,
>
> Am Mon, 1 Aug 2022 19:56:53 +0200 schrieb Arnout Vandecappelle:
>
>>> +# fixed in version 2.2.5
>>> +APACHE_IGNORE_CVES += CVE-2007-4465 CVE-2008-2168
>
>> Then why do we need to exclude it? Is there something wrong with the
> CVE's CPE
>> information? Or with our own CPE information? Or with our cpedb script?
>
> 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?
>
> Thomas suggested to get the NIST database fixed:
> https://lists.buildroot.org/pipermail/buildroot/2022-August/648210.html
>
> but these entries can show up again and again... And providing proof that
> a disputed entry from 2007 should be removed from their database is
> beyond my capabilities...
The disputed entry is OK(ish). It's the ones where the version information in
NVD is wrong that we don't want the exception.
Regards,
Arnout
>
> Regards, Bernd
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-01 18:16 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 [this message]
[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
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=6b20e25f-e562-d4aa-3da5-1000ab3f43bf@mind.be \
--to=arnout@mind.be \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@uclibc.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 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.