Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-08-15
Date: Tue, 17 Aug 2021 13:10:03 +0200	[thread overview]
Message-ID: <87wnok2upg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210817125624.54e64a83@windsurf> (Thomas Petazzoni's message of "Tue, 17 Aug 2021 12:56:24 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > On Tue, 17 Aug 2021 12:35:20 +0200
 > Peter Korsgaard <peter@korsgaard.com> wrote:

 >> >              name              |       CVE        |                             link                            
 >> > -------------------------------+------------------+--------------------------------------------------------------
 >> >                      mosquitto | CVE-2021-34432   | https://security-tracker.debian.org/tracker/CVE-2021-34432    
 >> 
 >> Hmm, looks like we have a bug in the version comparison logic. We have
 >> 2.0.11 and the CPE data states <= 2.0.7:

 > No, the CPE data states: "Up to (including) 2.07". Notice how 2.07 is
 > different than 2.0.7 ?

 > 2.07 is indeed "newer" than 2.0.11, so our comparison logic works fine.
 > You can look at
 > https://nvd.nist.gov/vuln/detail/CVE-2021-34432/cpes?expandCpeRanges=true
 > which shows the full list of CPE IDs that are considered vulnerable,
 > and 2.0.11 is among the one considered vulnerable, based on the
 > (probably incorrect) 2.07 information.

Ahh, indeed!


 > If you have some evidence that shows that the fix only affects versions
 > up to 2.0.7, then we can contact the NVD maintainers and get the issue
 > fixed.

Yes, it was (silently) fixed in 2.0.8 as mentioned in the linked
bugtracker issue:

https://github.com/eclipse/mosquitto/commit/9b08faf0bdaf5a4f2e6e3dd1ea7e8c57f70418d6

What was the process for reporting issues in the CPE data again?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-08-17 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 10:35 [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-08-15 Peter Korsgaard
2021-08-17 10:56 ` Thomas Petazzoni
2021-08-17 11:10   ` Peter Korsgaard [this message]
2021-08-17 11:12     ` Thomas Petazzoni
2021-08-17 15:42       ` Peter Korsgaard
2021-08-18 10:17         ` 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=87wnok2upg.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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