From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libsoup: security bump to version 2.62.3
Date: Tue, 28 Aug 2018 15:17:01 +0300 [thread overview]
Message-ID: <87lg8qy9c2.fsf@tkos.co.il> (raw)
In-Reply-To: <87va7u66d0.fsf@dell.be.48ers.dk>
Hi Peter,
Peter Korsgaard writes:
>>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> > Peter Korsgaard writes:
> >>>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> >>
> >> > Fixes CVE-2018-12910: The get_cookies function in soup-cookie-jar.c in
> >> > libsoup 2.63.2 allows attackers to have unspecified impact via an empty
> >> > hostname.
> >>
> >> > Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> >> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> >>
> >> Thanks! I started looking at this myself, but got sidetracked.
> >>
> >> Is 2.62.x the first release containing this fix? Should we also cherry
> >> pick this for 2018.02.x / 2018.05.x or is there a smaller patch that
> >> could be applied instead?
>
> > The upstream fix from the (stable) gnome-3-28 branch is:
>
> > https://gitlab.gnome.org/GNOME/libsoup/commit/c5c41ad1d36c1efb3226a74ac8ea591419882892
>
> > You can cherry pick it to the gnome-3-22 branch that carries 2.56.x.
>
> Thanks. Is that the best solution or does upgrading to 2.62.x look
> "safe" for 2018.02 / 2018.05 / 2018.08?
Patch backport would probably be safer for master and stable. I'll post
a patch.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-08-28 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 9:27 [Buildroot] [PATCH] libsoup: security bump to version 2.62.3 Baruch Siach
2018-08-28 11:18 ` Peter Korsgaard
2018-08-28 11:29 ` Baruch Siach
2018-08-28 12:08 ` Peter Korsgaard
2018-08-28 12:17 ` Baruch Siach [this message]
2018-08-28 20:39 ` 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=87lg8qy9c2.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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