CVE-2024-31225: high-severity vulnerability in RIOT-OS RIOT
Lack of size check and buffer overflow in RIOT
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.4epss 1.3%
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. The `_on_rd_init()` function does not implement a size check before copying data to the `_result_buf` static buffer. If an attacker can craft a long enough payload, they could cause a buffer overflow. 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 yet to be patched. Users are advised to add manual bounds checking.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Affected products
RIOT-OS · RIOTRelated CVEs — RIOT-OS RIOT
In the same product, most dangerous first.
CVE-2024-32017CRITICALBuffer overflows in RIOTEPSS 1.6%CVE-2024-32018HIGHIneffective size check due to assert() and buffer overflow in RIOTEPSS 1.5%CVE-2023-33975CRITICALRIOT-OS vulnerable to Out of Bounds Write in _rbuf_addEPSS 1.5%CVE-2023-24818HIGHRIOT-OS vulnerable to null pointer dereference during fragment forwardingEPSS 1.2%CVE-2023-24823CRITICALRIOT-OS vulnerable to Packet Type Confusion during IPHC sendEPSS 1.0%CVE-2023-24819CRITICALRIOT-OS vulnerable to Buffer Overflow during IPHC receiveEPSS 1.0%