From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] wpa_supplicant: add security patches
Date: Wed, 11 Nov 2015 15:20:02 +0100 [thread overview]
Message-ID: <20151111152002.0384f7b6@free-electrons.com> (raw)
In-Reply-To: <1447250946-15575-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 11 Nov 2015 11:09:05 -0300, Gustavo Zacarias wrote:
> Fixes:
> CVE-2015-5310 - wpa_supplicant unauthorized WNM Sleep Mode GTK control
> CVE-2015-5315 - wpa_supplicant: EAP-pwd missing last fragment length
> validation
> CVE-2015-5316 - EAP-pwd peer error path failure on unexpected Confirm
> message
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> ...Key-Data-in-WNM-Sleep-Mode-Response-frame.patch | 32 +++++++++++++
> ...-peer-Fix-last-fragment-length-validation.patch | 54 ++++++++++++++++++++++
> ...erver-Fix-last-fragment-length-validation.patch | 51 ++++++++++++++++++++
> ...r-Fix-error-path-for-unexpected-Confirm-m.patch | 34 ++++++++++++++
> 4 files changed, 171 insertions(+)
> create mode 100644 package/wpa_supplicant/0002-WNM-Ignore-Key-Data-in-WNM-Sleep-Mode-Response-frame.patch
> create mode 100644 package/wpa_supplicant/0003-EAP-pwd-peer-Fix-last-fragment-length-validation.patch
> create mode 100644 package/wpa_supplicant/0004-EAP-pwd-server-Fix-last-fragment-length-validation.patch
> create mode 100644 package/wpa_supplicant/0005-EAP-pwd-peer-Fix-error-path-for-unexpected-Confirm-m.patch
Both applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-11-11 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 14:09 [Buildroot] [PATCH 1/2] wpa_supplicant: add security patches Gustavo Zacarias
2015-11-11 14:09 ` [Buildroot] [PATCH 2/2] hostapd: " Gustavo Zacarias
2015-11-11 14:20 ` Thomas Petazzoni [this message]
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=20151111152002.0384f7b6@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