Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/giflib: security bump to version 5.2.1
Date: Mon, 19 Aug 2019 22:58:29 +0200	[thread overview]
Message-ID: <87lfvog9e2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAPi7W82Ft-zEoFOiedWNGde6fpSeeyGiGaCnD3onQpo9UT6o6g@mail.gmail.com> (Fabrice Fontaine's message of "Mon, 19 Aug 2019 22:26:47 +0200")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > Le lun. 19 ao?t 2019 ? 21:40, Thomas Petazzoni
 > <thomas.petazzoni@bootlin.com> a ?crit :
 >> 
 >> On Mon, 19 Aug 2019 19:07:24 +0200
 >> Peter Korsgaard <peter@korsgaard.com> wrote:
 >> 
 >> >  > I must say this is quite big of a change for master at this point, and
 >> >  > for a security bump in general. I'm not sure between applying this, or
 >> >  > just cherry-picking the two commits that fix the CVEs.
 >> >
 >> > Yes, I believe that is also what we agreed when Bernd posted a similar
 >> > patch last month:
 >> >
 >> > https://patchwork.ozlabs.org/patch/1124785/
 >> 
 >> So in here you also say that the security issue is only in a tool we
 >> don't install, so we're not affected. In this case, I could just apply
 >> Fabrice's patch to next, and we do nothing for master ?
 > Why these CVEs only affects tools? As you can see in both links that I
 > provided, those CVEs are located in dgif_lib.c which is a part of
 > libgif and libgif is installed in staging. So I think that some of our
 > users could be concerned by these CVEs. Moreover, we are also
 > providing host-giflib which build and install host tools.

Yes, sorry - I got #113 and #114 mixed up (and CVE-2019-15133 was not
announced back then).

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-08-19 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 12:04 [Buildroot] [PATCH 1/1] package/giflib: security bump to version 5.2.1 Fabrice Fontaine
2019-08-19 13:46 ` Thomas Petazzoni
2019-08-19 13:57   ` Fabrice Fontaine
2019-08-19 20:57     ` Peter Korsgaard
2019-08-19 17:07   ` Peter Korsgaard
2019-08-19 19:40     ` Thomas Petazzoni
2019-08-19 20:26       ` Fabrice Fontaine
2019-08-19 20:58         ` Peter Korsgaard [this message]
2019-08-19 20:44       ` Peter Korsgaard

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=87lfvog9e2.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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