Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] dnsmasq: security bump to version 2.78
Date: Tue, 03 Oct 2017 10:11:17 +0200	[thread overview]
Message-ID: <87bmlod522.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <9b9ffd72d158a792696b98b6612e4e66ee11892a.1506965906.git.baruch@tkos.co.il> (Baruch Siach's message of "Mon, 2 Oct 2017 20:38:25 +0300")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > Supported Lua version is now 5.2.
 > Add licenses hash.

 > Fixes a number of security issues:

 > CVE-2017-13704 - Crash when DNS query exceeded 512 bytes (a regression
 > in 2.77, so technically not fixed by this bump)

 > CVE-2017-14491 - Heap overflow in DNS code

 > CVE-2017-14492 - Heap overflow in IPv6 router advertisement code

 > CVE-2017-14493 - Stack overflow in DHCPv6 code

 > CVE-2017-14494 - Information leak in DHCPv6

 > CVE-2017-14496 - Invalid boundary checks allows a malicious DNS queries
 > to trigger DoS

 > CVE-2017-14495 - Out-of-memory Dos vulnerability

 > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
 > ---
 > v2: Bump to 2.78
 >     Note security fixes in the commit log

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2017-10-03  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 17:38 [Buildroot] [PATCH v2 1/2] dnsmasq: security bump to version 2.78 Baruch Siach
2017-10-02 17:38 ` [Buildroot] [PATCH v2 2/2] dnsmasq: simplify build configuration Baruch Siach
2017-10-02 19:04 ` [Buildroot] [PATCH v2 1/2] dnsmasq: security bump to version 2.78 Thomas Petazzoni
2017-10-03  8:11 ` Peter Korsgaard [this message]
2017-10-17  9:01 ` 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=87bmlod522.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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