From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcurl: security bump to version 7.62.0
Date: Wed, 31 Oct 2018 09:50:29 +0100 [thread overview]
Message-ID: <20181031095029.0195b7be@windsurf> (raw)
In-Reply-To: <20181031084056.25144-1-peter@korsgaard.com>
Hello,
On Wed, 31 Oct 2018 09:40:55 +0100, Peter Korsgaard wrote:
> Fixes the following security issues:
>
> CVE-2018-16839: SASL password overflow via integer overflow
> https://curl.haxx.se/docs/CVE-2018-16839.html
>
> CVE-2018-16840: use-after-free in handle close
> https://curl.haxx.se/docs/CVE-2018-16840.html
>
> CVE-2018-16842: warning message out-of-buffer read
> https://curl.haxx.se/docs/CVE-2018-16842.html
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/libcurl/libcurl.hash | 4 ++--
> package/libcurl/libcurl.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-31 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 8:40 [Buildroot] [PATCH] libcurl: security bump to version 7.62.0 Peter Korsgaard
2018-10-31 8:50 ` Thomas Petazzoni [this message]
2018-11-14 9:36 ` 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=20181031095029.0195b7be@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