Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcurl: security bump to version 7.60.0
Date: Sat, 19 May 2018 13:47:39 +0200	[thread overview]
Message-ID: <20180519134739.69d2d28f@windsurf> (raw)
In-Reply-To: <c80a6fad0f71e02beda054135fc6e2e2f4ed2a0f.1526612436.git.baruch@tkos.co.il>

Hello,

On Fri, 18 May 2018 06:00:36 +0300, Baruch Siach wrote:
> Drop upstream patch.
> 
> This release fixes the security issues listed below.
> 
> CVE-2018-1000300: curl might overflow a heap based memory buffer when
> closing down an FTP connection with very long server command replies.
> 
>   https://curl.haxx.se/docs/adv_2018-82c2.html
> 
> CVE-2018-1000301: curl can be tricked into reading data beyond the end
> of a heap based buffer used to store downloaded content.
> 
>   https://curl.haxx.se/docs/adv_2018-b138.html
> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
>  ...-openssl-fix-build-with-LibreSSL-2.7.patch | 75 -------------------
>  package/libcurl/libcurl.hash                  |  4 +-
>  package/libcurl/libcurl.mk                    |  2 +-
>  3 files changed, 3 insertions(+), 78 deletions(-)
>  delete mode 100644 package/libcurl/0001-openssl-fix-build-with-LibreSSL-2.7.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-05-19 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  3:00 [Buildroot] [PATCH] libcurl: security bump to version 7.60.0 Baruch Siach
2018-05-19 11:47 ` Thomas Petazzoni [this message]
2018-06-11 21:12 ` 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=20180519134739.69d2d28f@windsurf \
    --to=thomas.petazzoni@bootlin.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