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

> An integer overflow in MBed OS HCI packet processing causes a buffer overflow, leading to denial of service.

- **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-733q-89m7-5784

## What is CVE-2024-48983?

CVE-2024-48983 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. During processing of HCI packets, the software dynamically determines the length of the packet data by reading 2 bytes from the packet header. 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 plus the header length. WsfMsgAlloc then increments this again by sizeof(wsfMsg_t). This may cause an integer overflow that results in the buffer being significantly too small to contain the entire packet. This may cause a buffer overflow of up to 65 KB . This bug is trivial to exploit for a denial of service but can generally not be exploited further because the exploitable buffer is dynamically allocated.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Arm Mbed.

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

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

## Is CVE-2024-48983 being exploited?

There is no known exploitation of CVE-2024-48983 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-48982](https://insights.sbomify.com/CVE-2024-48982/): 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-48983 and fix it if it is affected.

What it is: CVE-2024-48983 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-48983 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-48983/ (Markdown: https://insights.sbomify.com/CVE-2024-48983/index.md)
```

## Sources

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

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