CVE-2024-48984

Published Nov 20, 2024 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Arm
Arm mbed Os
CPEs cpe:2.3:o:arm:mbed_os:6.16.0:*:*:*:*:*:*:*
Vendors & Products Arm
Arm mbed Os
Type Values Removed Values Added
First Time appeared Mbed
Mbed mbed
Weaknesses CWE-120
CPEs cpe:2.3:o:mbed:mbed:6.16.0:*:*:*:*:*:*:*
Vendors & Products Mbed
Mbed mbed
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Nov 25, 2024, 9:09 PM
Reserved
Oct 11, 2024, 12:00 AM
Status
Analyzed
Published
Nov 20, 2024, 9:15 PM
Modified
Jun 17, 2026, 7:59 AM