Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.549% probability within 30 days)
| 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
|
| 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 |
|