Memory corruption via assertion-only scan length check
Published May 1, 2024 · Updated Feb 13, 2025
Buffer overflow in RIOT 2023.10 and earlier allows remote authenticated users to corrupt memory via oversized NimBLE scan data. nimble_scanlist_update() checks len only with an assertion, then passes it to memcpy() for the fixed-length e->ad buffer when assertions are disabled. Exploitation requires attacker control of len across a security boundary and use of the NimBLE scan list; the overwrite allows a device crash or arbitrary code execution.
Summary
What happened
Buffer overflow in RIOT 2023.10 and earlier allows remote authenticated users to corrupt memory via oversized NimBLE scan data. nimble_scanlist_update() checks len only with an assertion, then passes it to memcpy() for the fixed-length e->ad buffer when assertions are disabled. Exploitation requires attacker control of len across a security boundary and use of the NimBLE scan list; the overwrite allows a device crash or arbitrary code execution.
The record
- CVE
- CVE-2024-32018
- Published
- May 1, 2024
- Updated
- Feb 13, 2025
- Vendor
- RIOT-OS
- Product
- RIOT
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2023.10
- Affected versionversion=<= 2023.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo