CVE-2024-48984: Buffer Overflow
An issue was discovered in MBed OS 6.16.0. When parsing hci reports, the hci parsing software dynamically determines the length of a list of reports by reading a byte from an input stream. It then fetches the length of the first report, uses it to calculate the beginning of the second report, etc. In doing this, it tracks the largest report so it can later allocate a buffer that fits every individual report (but only one at a time). It does not, however, validate that these addresses are all contained within the buffer passed to hciEvtProcessLeExtAdvReport. It is then possible, though unlikely, that the buffer designated to hold the reports is allocated in such a way that one of these out-of-bounds length fields is contained within the new buffer. When the (n-1)th report is copied, it overwrites the length field of the nth report. This now corrupted length field is then used for a memcpy into the new buffer, which may lead to a buffer overflow.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-48984?
CVE-2024-48984 is considered a medium severity vulnerability due to its potential to cause information leaks and malformed data processing.
How do I fix CVE-2024-48984?
To fix CVE-2024-48984, update MBed OS to the latest version or apply the relevant patches from the vendor.
Which versions of MBed OS are affected by CVE-2024-48984?
CVE-2024-48984 affects MBed OS version 6.16.0 and potentially earlier versions.
What kind of vulnerability is CVE-2024-48984?
CVE-2024-48984 is a parsing vulnerability that can lead to improper handling of input data in Bluetooth communication.
Is there a proof of concept for CVE-2024-48984?
Yes, there is a proof of concept for CVE-2024-48984 included in the discussions and code changes associated with the vulnerability.