mirror of
https://github.com/vanhoefm/fragattacks.git
synced 2025-02-17 17:43:06 -05:00
WNM: Fix BSS Termination Duration subelement length validation
The length check for the BSS Termination Duration subelement was accidentally removed and this could result in reading up to 10 bytes beyond the end of a received frame. The actual read bytes would be stored locally, but they were not used for anything, so other than reading beyond the end of an allocated heap memory buffer, this did not result in any behavior difference or exposure of the bytes. Credit to OSS-Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14922 Fixes: 093226783dc7 ("WNM: Simplify how candidate subelements are stored") Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
This commit is contained in:
parent
2dfe2ad6cb
commit
e8ebef87cb
@ -451,6 +451,11 @@ static void wnm_parse_neighbor_report_elem(struct neighbor_report *rep,
|
|||||||
rep->preference_present = 1;
|
rep->preference_present = 1;
|
||||||
break;
|
break;
|
||||||
case WNM_NEIGHBOR_BSS_TERMINATION_DURATION:
|
case WNM_NEIGHBOR_BSS_TERMINATION_DURATION:
|
||||||
|
if (elen < 10) {
|
||||||
|
wpa_printf(MSG_DEBUG,
|
||||||
|
"WNM: Too short BSS termination duration");
|
||||||
|
break;
|
||||||
|
}
|
||||||
rep->bss_term_tsf = WPA_GET_LE64(pos);
|
rep->bss_term_tsf = WPA_GET_LE64(pos);
|
||||||
rep->bss_term_dur = WPA_GET_LE16(pos + 8);
|
rep->bss_term_dur = WPA_GET_LE16(pos + 8);
|
||||||
rep->bss_term_present = 1;
|
rep->bss_term_present = 1;
|
||||||
|
Loading…
x
Reference in New Issue
Block a user