From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] c-ares: security bump to version 1.13.0
Date: Wed, 21 Jun 2017 07:44:26 +0200 [thread overview]
Message-ID: <20170621074426.6db80181@windsurf.lan> (raw)
In-Reply-To: <20170620212421.17455-1-peter@korsgaard.com>
Hello,
On Tue, 20 Jun 2017 23:24:21 +0200, Peter Korsgaard wrote:
> Fixes the following security issues:
>
> CVE-2017-1000381: The c-ares function `ares_parse_naptr_reply()`, which is
> used for parsing NAPTR responses, could be triggered to read memory outside
> of the given input buffer if the passed in DNS response packet was crafted
> in a particular way.
>
> https://c-ares.haxx.se/adv_20170620.html
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/c-ares/c-ares.hash | 2 +-
> package/c-ares/c-ares.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-21 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:24 [Buildroot] [PATCH] c-ares: security bump to version 1.13.0 Peter Korsgaard
2017-06-21 5:44 ` Thomas Petazzoni [this message]
2017-06-26 8:00 ` 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=20170621074426.6db80181@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.