CVE-2024-31225: Riot-os Riot buffer overflow (CVSS 8.3)

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. 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 breakdown

Attack vectorNetwork

Attack complexityHigh

Privileges requiredNone

User interactionRequired

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Riot-os Riot< 2024.01

Remediation

Fixed in

Riot-os Riot≥ 2024.01

Patch & vendor advisories

https://github.com/RIOT-OS/RIOT/security/advisories/GHSA-2572-7q7c-3965

References

http://seclists.org/fulldisclosure/2024/May/7Mailing ListThird Party Advisory
https://github.com/RIOT-OS/RIOT/blob/master/sys/net/application_layer/cord/lc/cord_lc.c#L218Product
https://github.com/RIOT-OS/RIOT/security/advisories/GHSA-2572-7q7c-3965ExploitVendor Advisory
http://www.openwall.com/lists/oss-security/2024/05/07/3Mailing ListThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-31225 being actively exploited?

CVE-2024-31225 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.30%.

How severe is CVE-2024-31225?

CVE-2024-31225 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 1.30% probability of exploitation.

Which products are affected by CVE-2024-31225?

Affected products include Riot-os Riot.

How do I fix CVE-2024-31225?

Upgrade affected software to a fixed version, for example Riot-os Riot 2024.01 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-31225 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo