From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2020-09-06
Date: Mon, 7 Sep 2020 15:52:58 +0200 [thread overview]
Message-ID: <20200907155258.48f8a088@windsurf.home> (raw)
In-Reply-To: <45c5b4b3-a11a-1ec3-2f7b-c8abf229b06f@green-communications.fr>
Hello,
On Mon, 7 Sep 2020 11:47:59 +0200
Nicolas Cavallari <nicolas.cavallari@green-communications.fr> wrote:
> On 07/09/2020 09:08, Thomas Petazzoni wrote:>
> libgit2 | CVE-2014-9390 |
> https://security-tracker.debian.org/tracker/CVE-2014-9390
> So libgit2 is affected by a 6 year old security vulnerability that has
> been fixed before the package was actually introduced in buildroot...
>
> This apparently comes directly from the nvd database, do i wait for it
> to be fixed, or should i add it to LIBGIT2_IGNORE_CVES ? The manual
> doesn't say anything about this case.
Thanks for getting back to us about this.
According to what
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774048 says, it was
fixed upstream in version 0.21.3, and a quick inspection indeed shows
this commit between 0.21.2 and 0.21.3:
commit 928429c5c96a701bcbcafacb2421a82602b36915
Author: Vicent Mart? <vicent@github.com>
Date: Tue Nov 25 00:14:52 2014 +0100
tree: Check for `.git` with case insensitivy
So I believe that the NVD database should be updated to indicate that
only versions up to 0.21.2 are affected.
Matt has documented at
https://elinux.org/Buildroot:Security_Vulnerability_Management how to
request updates of NVD entries, but I've never followed the process
myself.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-09-07 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 7:08 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-09-06 Thomas Petazzoni
2020-09-07 9:47 ` Nicolas Cavallari
2020-09-07 13:52 ` Thomas Petazzoni [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=20200907155258.48f8a088@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