Apple WLC_E_COUNTRY_CODE_CHANGED Information Leak

2017.09.24
Credit: laginimaineb
Risk: Medium
Local: Yes
Remote: No
CWE: CWE-200


CVSS Base Score: 5/10
Impact Subscore: 2.9/10
Exploitability Subscore: 10/10
Exploit range: Remote
Attack complexity: Low
Authentication: No required
Confidentiality impact: Partial
Integrity impact: None
Availability impact: None

Apple: Information Leak when handling WLC_E_COUNTRY_CODE_CHANGED event packets CVE-2017-7116 Broadcom produces Wi-Fi HardMAC SoCs which are used to handle the PHY and MAC layer processing. These chips are present in both mobile devices and Wi-Fi routers, and are capable of handling many Wi-Fi related events without delegating to the host OS. On iOS, the "AppleBCMWLANBusInterfacePCIe" driver is used in order to handle the PCIe interface and low-level communication protocols with the Wi-Fi SoC (also referred to as "dongle"). Similarly, the "AppleBCMWLANCore" driver handles the high-level protocols and the Wi-Fi configuration. When the dongle wishes to notify the host OS of an event, it does so by encoding a special "packet" and transmitting it to the host. These packets have an ether type of 0x886C, and do not contain actual packet data, but rather encapsulate information about events which must be handled by the driver. One of the supported event packets is the WLC_E_COUNTRY_CODE_CHANGED message, which notifies that host that the country code has been modified. On iOS, these events are handled by the "handleCountryCodeChangedEvent" function in the "AppleBCMWLANCore" driver. Each packet of this type starts with the common event message header (which is 48 bytes long), followed by the 3-character country code, delimited by a NUL. Here is a snippet of "handleCountryCodeChangedEvent"'s high-level logic: int64_t handleCountryCodeChangedEvent(void* this, uint8_t* event_packet) { char* country_code = (char*)this + 3244; char* alt_country_code = (char*)this + 3248; strncpy(country_code, event_packet + 48, 3); country_code[3] = '\0'; if ( strncmp(country_code, "XZ", strlen("XZ")) && strncmp(alt_country_code, country_code 4)) { strncpy(alt_country_code, country_code, 3); alt_country_code[3] = '\0'; updateChannelSpecsAsync(this); } ... } int64_t updateChannelSpecsAsync(void* this) { char request_buffer[0x1C2]; bzero(request_buffer, 0x1C2); char* country_code = (char*)this + 3244; strlcpy(request_buffer, country_code, 4); return issueCommand(..., request_buffer, ...); //Getting the "chanspecs" IO-Var ... } As can be seen above, the function fails to verify that the length of the event message is sufficiently long (that is, larger than just the message header itself). As a result, an attacker controlling the dongle can send a WLC_E_COUNTRY_CODE_CHANGED event packet with no body payload. Doing so will cause the 3 bytes of the country code to be copied OOB (from event_packet + 48). As long as these bytes are not "XZ" or the previously stored country code ("alt_country_code"), "updateChannelSpecsAsync" will be called, causing the OOB data to be sent back to the dongle in the WLC_GET_VAR ioctl - thus leaking the bytes back to the dongle. This bug is subject to a 90 day disclosure deadline. After 90 days elapse or a patch has been made broadly available, the bug report will become visible to the public. Found by: laginimaineb


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2022, cxsecurity.com

 

Back to Top