# CVE-2024-48982: Integer overflow in n/a

> Attackers can cause a denial of service in MBed OS by sending malformed HCI packets with invalid length values, triggering buffer overflows.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2024
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-r8wg-wr62-xwrv

## What is CVE-2024-48982?

CVE-2024-48982 is a high-severity vulnerability in n/a, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in MBed OS 6.16.0. Its hci parsing software dynamically determines the length of certain hci packets by reading a byte from its header. This value is assumed to be greater than or equal to 3, but the software doesn't ensure that this is the case. Supplying a length less than 3 leads to a buffer overflow in a buffer that is allocated later. It is simultaneously possible to cause another integer overflow by supplying large length values because the provided length value is increased by a few bytes to account for additional information that is supposed to be stored there. This bug is trivial to exploit for a denial of service but is not certain to suffice to bring the system down and can generally not be exploited further because the exploitable buffer is dynamically allocated.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-48982?

It affects 1 product.


Products: Arm Mbed.

## How do I fix CVE-2024-48982?

No fix has been published for CVE-2024-48982 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48982 being exploited?

There is no known exploitation of CVE-2024-48982 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-48981](https://insights.sbomify.com/CVE-2024-48981/): Memory corruption in n/a (high 7.5)
- [CVE-2024-48983](https://insights.sbomify.com/CVE-2024-48983/): Integer overflow in n/a (high 7.5)
- [CVE-2024-48985](https://insights.sbomify.com/CVE-2024-48985/): Memory corruption in n/a (high 7.5)
- [CVE-2024-48986](https://insights.sbomify.com/CVE-2024-48986/): Memory corruption in n/a (high 7.5)
- [CVE-2021-27435](https://insights.sbomify.com/CVE-2021-27435/): ARM mbed Integer Overflow or Wraparound (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48982 and fix it if it is affected.

What it is: CVE-2024-48982 is a high-severity vulnerability in n/a, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48982 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48982/ (Markdown: https://insights.sbomify.com/CVE-2024-48982/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48982
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48982
- OSV: https://osv.dev/vulnerability/CVE-2024-48982

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48982/
Summaries are generated and may contain mistakes; the official description above is the record.
