All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Weber <matthew.weber@collins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-07-12
Date: Tue, 21 Jul 2020 10:30:34 -0500	[thread overview]
Message-ID: <CANQCQpbch4btr_v9wAYPBiHC62Q1cGKN0Kc6_9c9jTWz1Qa44Q@mail.gmail.com> (raw)
In-Reply-To: <20200721172355.16a5a651@windsurf.home>

Thomas,

On Tue, Jul 21, 2020 at 10:27 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Matt,
>
> On Tue, 21 Jul 2020 10:13:03 -0500
> Matthew Weber <matthew.weber@collins.com> wrote:
>
> > I've submitted the following request to fix this
> >
> > 1) Navigated to https://cveform.mitre.org/
> > 2) "Select a request type" as "Request and update to an existing CVE Entry"
> > 3) "Type of update requested" as "Update Description"
> > 4) "CVE ID to be updated" as 2010-0751
> > 5) "Description" as "We've found that the v1.24 fixes the CVE and all
> > prior versions contain the bug.  The CVE currently lists that 1.24 is
> > still vulnerable.  This can be proved by checking the CHANGES file
> > within the source archive
> > (https://sourceforge.net/projects/libnids/files/libnids/1.24/libnids-1.24.tar.gz/download)
> > that outlines this ("fixed another remotely triggerable NULL
> > dereference in ip_fragment.c") comment.  Also within that archive the
> > source code src/ip_fragment on line 378 has the fix
> > (https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=576281;filename=CVE-2010-1144.patch;msg=5)
> > (NOTE 2010-1144 is a rejected CVE which was split to include
> > 2010-0751)."
>
> Thanks for doing this !
>
> > Thomas, do you think it would be beneficial to add a section with
> > these notes in the manual?
>
> Reading your e-mail, I was precisely thinking "it would be great to
> write this down somewhere". I don't know if the manual is the right
> place though, as it is really for Buildroot maintainers/developers.
> Would the Wiki be a better location ?

Ah, yeah that could work.  I was looking at making a subsection under
"21.6. Reporting issues/bugs or getting help" if we do add it in the
manual.  There are going to be cases where a Buildroot CVE report
misreports because of our scripts, plus the case of an actual
dictionary bug.

Maybe we start on the wiki?

Regards,
Matt

  reply	other threads:[~2020-07-21 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5f0c105a.1c69fb81.17d79.8de3SMTPIN_ADDED_MISSING@mx.google.com>
2020-07-17 13:01 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-07-12 Guillaume Bres
2020-07-17 15:37   ` Thomas Petazzoni
2020-07-17 15:45     ` Matthew Weber
2020-07-17 15:46       ` Matthew Weber
2020-07-21 15:13     ` Matthew Weber
2020-07-21 15:23       ` Thomas Petazzoni
2020-07-21 15:30         ` Matthew Weber [this message]
2020-07-21 15:53           ` Thomas Petazzoni
2020-07-21 16:00             ` Matthew Weber
2020-07-21 17:28               ` Thomas Petazzoni

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=CANQCQpbch4btr_v9wAYPBiHC62Q1cGKN0Kc6_9c9jTWz1Qa44Q@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.