# CVE-2024-32018: Ineffective size check due to assert() and buffer overflow in RIOT

> Attackers can trigger a buffer overflow in RIOT OS by providing oversized input when assertions are disabled, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-899m-q6pp-hmp3

## What is CVE-2024-32018?

CVE-2024-32018 is a high-severity memory corruption vulnerability in RIOT-OS RIOT, published on 1 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RIOT is a real-time multi-threading operating system that supports a range of devices that are typically 8-bit, 16-bit and 32-bit microcontrollers. Most codebases define assertion macros which compile to a no-op on non-debug builds. If assertions are the only line of defense against untrusted input, the software may be exposed to attacks that leverage the lack of proper input checks. In detail, in the `nimble_scanlist_update()` function below, `len` is checked in an assertion and subsequently used in a call to `memcpy()`. If an attacker is able to provide a larger `len` value while assertions are compiled-out, they can write past the end of the fixed-length `e->ad` buffer. If the unchecked input above is attacker-controlled and crosses a security boundary, the impact of the buffer overflow vulnerability could range from denial of service to arbitrary code execution. This issue has not yet been patched. Users are advised to add manual `len` checking.

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

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

It affects 1 product.


Products: Riot-Os Riot.

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

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

## Is CVE-2024-32018 being exploited?

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

## Other vulnerabilities in RIOT-OS RIOT

- [CVE-2024-32017](https://insights.sbomify.com/CVE-2024-32017/): Buffer overflows in RIOT (critical 9.8)
- [CVE-2023-33975](https://insights.sbomify.com/CVE-2023-33975/): RIOT-OS vulnerable to Out of Bounds Write in _rbuf_add (critical 9.8)
- [CVE-2023-24819](https://insights.sbomify.com/CVE-2023-24819/): RIOT-OS vulnerable to Buffer Overflow during IPHC receive (critical 9.8)
- [CVE-2023-24823](https://insights.sbomify.com/CVE-2023-24823/): RIOT-OS vulnerable to Packet Type Confusion during IPHC send (critical 9.8)
- [CVE-2021-27357](https://insights.sbomify.com/CVE-2021-27357/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32018 is a high-severity memory corruption vulnerability in RIOT-OS RIOT, published on 1 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32018 in the wild and no public exploit code.

Affected product: RIOT-OS RIOT. 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-32018/ (Markdown: https://insights.sbomify.com/CVE-2024-32018/index.md)
```

## Sources

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

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