Security Resilience

CVE-2023-24825

Memory Safety in Riot-Os Riot ≤ 2023.04

Published
30 May 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0096 62th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-24825 is a high-severity Unchecked Return Value (CWE-252) vulnerability in Riot-Os Riot. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 38% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

RIOT-OS, an operating system for Internet of Things (IoT) devices, contains a network stack with the ability to process 6LoWPAN frames. Prior to version 2023.04, an attacker can send a crafted frame to the device to trigger a NULL pointer…

more

dereference leading to denial of service. This issue is fixed in version 2023.04. There are no known workarounds.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-24822Same product: Riot-Os Riot
CVE-2023-33973Same product: Riot-Os Riot
CVE-2025-66646Same product: Riot-Os Riot
CVE-2023-24818Same product: Riot-Os Riot
CVE-2023-24826Same product: Riot-Os Riot
CVE-2024-32018Same product: Riot-Os Riot
CVE-2025-66647Same product: Riot-Os Riot
CVE-2024-32017Same product: Riot-Os Riot
CVE-2025-53888Same product: Riot-Os Riot
CVE-2024-31225Same product: Riot-Os Riot

Affected Assets

riot-os
riot
≤ 2023.04

Mitigating Controls

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require checking and handling all function return values to detect error conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance can detect missing return-value checks.

prevents

Training developers in defensive programming and error-handling practices reduces instances of unchecked return values, but the practice is fallible and a different clause (e.g., A.8.28 secure coding, A.8.29 security testing) carries the stronger effect, matching the A.6.3 vs CWE-598 and A.8.28 vs CWE-79 anchors.

prevents

Secure coding explicitly requires checking return values to avoid CWE-252.

prevents

A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; unchecked return values are a regular implementation defect that secure coding and security testing would catch, but the clause's mechanism is contractual and the practices are fallible, matching the owner-graded `partial` on A.8.30 vs CWE-134.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw — and CWE-252 is a first-party code defect that surfaces as CVEs only when it appears in a third-party component; the disclosed share is a minority, capping the rung at `partial`.

References