From: Matthew Weber <matthew.weber@collins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libnids: NVD database has been updated
Date: Thu, 30 Jul 2020 13:01:59 -0500 [thread overview]
Message-ID: <CANQCQpZH6pt2-vs-9vi7Tw0TFz3HjkT2ftqzGM3vwzot-RU5MQ@mail.gmail.com> (raw)
In-Reply-To: <CAJe0E3cP6oppGocO9LuE+-ctjicSq1oRh8p2qD=gZdwi7N+_aQ@mail.gmail.com>
Guillaume, I've submitted another request with more detail and hopefully
they'll update all the references to the version
On Wed, Jul 22, 2020 at 2:34 AM Guillaume Bres <guillaume.bressaix@gmail.com>
wrote:
> Ugh, looks like they only updated the description and didn't adjust the
>> rest of the version references
>
>
> yes that's what happened ? we may need to wait a little longer
>
> Guillaume W. Bres
> Software engineer
> <guillaume.bressaix@gmail.com>
>
>
> Le mar. 21 juil. 2020 ? 22:09, Matthew Weber <matthew.weber@collins.com>
> a ?crit :
>
>> Ugh, looks like they only updated the description and didn't adjust the
>> rest of the version references
>>
>> https://nvd.nist.gov/vuln/detail/CVE-2010-0751#match-5471142
>>
>> On Tue, Jul 21, 2020 at 1:46 PM Thomas Petazzoni <
>> thomas.petazzoni at bootlin.com> wrote:
>>
>>> On Tue, 21 Jul 2020 20:05:55 +0200
>>> guillaume.bressaix at gmail.com wrote:
>>>
>>> > From: "Guillaume W. Bres" <guillaume.bressaix@gmail.com>
>>> >
>>> > Thanks to Matthew W. & Thomas, the NVD database has been updated
>>> > and CVE-2010-0751 is now declared fixed, see
>>> > https://security-tracker.debian.org/tracker/CVE-2010-0751
>>> >
>>> > Signed-off-by: Guillaume W. Bres <guillaume.bressaix@gmail.com>
>>>
>>> Are you sure it has already been fixed ?
>>>
>>> https://nvd.nist.gov/vuln/detail/CVE-2010-0751 still marks 1.24 as
>>> affected as far as I can see.
>>>
>>> Thomas
>>> --
>>> Thomas Petazzoni, CTO, Bootlin
>>> Embedded Linux and Kernel engineering
>>> https://bootlin.com
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>
>> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200730/0af3dc55/attachment.html>
next prev parent reply other threads:[~2020-07-30 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 18:05 [Buildroot] [PATCH 1/1] package/libnids: NVD database has been updated guillaume.bressaix at gmail.com
2020-07-21 18:43 ` Thomas Petazzoni
2020-07-21 20:08 ` Matthew Weber
2020-07-22 7:32 ` Guillaume Bres
2020-07-30 18:01 ` Matthew Weber [this message]
2020-08-05 16:18 ` Matthew Weber
2020-08-05 19:48 ` Thomas Petazzoni
2020-08-05 21:43 ` [Buildroot] [External] " Matthew Weber
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=CANQCQpZH6pt2-vs-9vi7Tw0TFz3HjkT2ftqzGM3vwzot-RU5MQ@mail.gmail.com \
--to=matthew.weber@collins.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 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.