From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] quagga: add upstream security fix for CVE-2017-16227
Date: Wed, 1 Nov 2017 10:47:23 +0100 [thread overview]
Message-ID: <20171101104723.55597da1@windsurf> (raw)
In-Reply-To: <20171030215309.21483-1-peter@korsgaard.com>
Hello,
On Mon, 30 Oct 2017 22:53:09 +0100, Peter Korsgaard wrote:
> From the advisory:
> http://www.openwall.com/lists/oss-security/2017/10/30/4
>
> It was discovered that the bgpd daemon in the Quagga routing suite does
> not properly calculate the length of multi-segment AS_PATH UPDATE
> messages, causing bgpd to drop a session and potentially resulting in
> loss of network connectivity.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> ...x-AS_PATH-size-calculation-for-long-paths.patch | 33 ++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
> create mode 100644 package/quagga/0004-bgpd-Fix-AS_PATH-size-calculation-for-long-paths.patch
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-11-01 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 21:53 [Buildroot] [PATCH] quagga: add upstream security fix for CVE-2017-16227 Peter Korsgaard
2017-11-01 9:47 ` Thomas Petazzoni [this message]
2017-11-26 9:13 ` 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=20171101104723.55597da1@windsurf \
--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