From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-11-08
Date: Mon, 9 Nov 2020 16:00:31 +0100 [thread overview]
Message-ID: <20201109160031.3828bba8@windsurf.home> (raw)
In-Reply-To: <20201109135402.ddk3myxwpwf7mkey@falbala.internal.home.lespocky.de>
Hello,
On Mon, 9 Nov 2020 14:54:03 +0100
Alexander Dahl <post@lespocky.de> wrote:
> that vulnerability was fixed by Fabrice Fontaine
> with 148058a46293 ("package/fastd: bump to version 21") for master and
> with 7e4af3ce3f91 ("package/fastd: fix CVE-2020-27638") which got
> cherry-picked for the stable branches.
>
> In the stable branches, there's a marker in FASTD_IGNORE_CVES in
> package/fastd/fastd.mk which probably silences such warnings. But how
> is this supposed to work if such vulnerabilities are closed via an
> ordinary release like that v21 in case of fastd? Just adding all CVE
> numbers to that variable could pile up a lot over time?
CVE-2020-27638 should not be reported on v21 and later versions,
because at https://nvd.nist.gov/vuln/detail/CVE-2020-27638, there is
"Up to (excluding) 21.0".
Are you seeing reports from Buildroot tooling where version v21 is said
to be affected by this CVE ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-11-09 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 13:54 [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-11-08 Alexander Dahl
2020-11-09 15:00 ` Thomas Petazzoni [this message]
2020-11-09 15:02 ` Fabrice Fontaine
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=20201109160031.3828bba8@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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