From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wpa_supplicant: add upstream 2020-2 security fix
Date: Fri, 05 Feb 2021 14:09:50 +0100 [thread overview]
Message-ID: <87sg6a7ja9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210205124530.GT2384@scaer> (Yann E. MORIN's message of "Fri, 5 Feb 2021 13:45:30 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Peter, All,
> On 2021-02-05 13:13 +0100, Peter Korsgaard spake thusly:
>> Fixes the following security issue:
>>
>> - wpa_supplicant P2P group information processing vulnerability (no CVE yet)
>>
>> A vulnerability was discovered in how wpa_supplicant processing P2P
>> (Wi-Fi Direct) group information from active group owners. The actual
>> parsing of that information validates field lengths appropriately, but
>> processing of the parsed information misses a length check when storing a
>> copy of the secondary device types. This can result in writing attacker
>> controlled data into the peer entry after the area assigned for the
>> secondary device type. The overflow can result in corrupting pointers
>> for heap allocations. This can result in an attacker within radio range
>> of the device running P2P discovery being able to cause unexpected
>> behavior, including termination of the wpa_supplicant process and
>> potentially arbitrary code execution.
>>
>> For more details, see the advisory:
>> https://w1.fi/security/2020-2/wpa_supplicant-p2p-group-info-processing-vulnerability.txt
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Applied to master, thanks.
Thanks.
> (I just moved the _PATCH near _VERSION and _SITE to keep similar things
> together)
Fine. I did it like this for consistency with hostapd.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-02-05 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 12:13 [Buildroot] [PATCH] package/wpa_supplicant: add upstream 2020-2 security fix Peter Korsgaard
2021-02-05 12:45 ` Yann E. MORIN
2021-02-05 13:09 ` Peter Korsgaard [this message]
2021-02-10 18:54 ` 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=87sg6a7ja9.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