CVE-2024-48985: Buffer Overflow
An issue was discovered in MBed OS 6.16.0. During processing of HCI packets, the software dynamically determines the length of the packet data by reading 2 bytes from the packet data. A buffer is then allocated to contain the entire packet, the size of which is calculated as the length of the packet body determined earlier and the header length. If the allocate fails because the specified packet is too large, no exception handling occurs and hciTrSerialRxIncoming continues to write bytes into the 4-byte large temporary header buffer, leading to a buffer overflow. This can be leveraged into an arbitrary write by an attacker. It is possible to overwrite the pointer to the buffer that is supposed to receive the contents of the packet body but which couldn't be allocated. One can then overwrite the state variable used by the function to determine which step of the parsing process is currently being executed. This advances the function to the next state, where it proceeds to copy data to that arbitrary location. The packet body is then written wherever the corrupted data pointer is pointing.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-48985?
The severity of CVE-2024-48985 is classified as medium due to potential risks associated with buffer allocation in MBed OS.
How do I fix CVE-2024-48985?
To fix CVE-2024-48985, update your MBed OS to a version later than 6.16.0 where this vulnerability has been addressed.
What software is affected by CVE-2024-48985?
CVE-2024-48985 affects MBed OS version 6.16.0.
What types of vulnerabilities does CVE-2024-48985 involve?
CVE-2024-48985 involves a potential buffer overflow vulnerability due to improper packet length determination.
How can CVE-2024-48985 impact my applications?
CVE-2024-48985 can lead to unexpected behavior in applications using affected MBed OS versions, including possible crashes or arbitrary code execution.