From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] nodejs: security bump 0.10.x series to 0.10.48
Date: Fri, 2 Dec 2016 22:35:00 +0100 [thread overview]
Message-ID: <20161202223500.3619441c@free-electrons.com> (raw)
In-Reply-To: <8737i66npq.fsf@dell.be.48ers.dk>
Hello,
On Fri, 02 Dec 2016 22:11:13 +0100, Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> > Hello,
> > On Fri, 2 Dec 2016 21:16:52 +0100, Peter Korsgaard wrote:
> >> c-ares: fix for single-byte buffer overwrite, CVE-2016-5180, more
> >> information at https://c-ares.haxx.se/adv_20160929.html
>
> > Thanks. What about our c-ares package itself?
>
> That one was fixed quite some time ago:
>
> commit 2d199dcff054d22a1ccc730fadfc7543b8c6e8f3
> Author: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Date: Wed Oct 12 20:17:17 2016 -0300
>
> c-ares: security bump to version 1.12.0
>
> Fixes:
> CVE-2016-5180 - ares_create_query single byte out of buffer write
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Ah, ok. Sorry, I didn't check that 1.12.0 fixed the issue. Thanks for
confirming.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-02 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 20:16 [Buildroot] [PATCH] nodejs: security bump 0.10.x series to 0.10.48 Peter Korsgaard
2016-12-02 20:36 ` Thomas Petazzoni
2016-12-02 21:11 ` Peter Korsgaard
2016-12-02 21:35 ` Thomas Petazzoni [this message]
2016-12-02 23:05 ` 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=20161202223500.3619441c@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox