Safeguard
Vulnerability Analysis•

CVE-2023-29001: High Uncontrolled Recursion in Contiki-NG

CVE-2023-29001 is an uncontrolled recursion in Contiki-NG source routing that can overflow the stack. Apply PR 2264 or move to a release that includes it.

Safeguard Security Team
4 min read

CVE-2023-29001 is an uncontrolled recursion flaw in Contiki-NG, the open source IoT operating system. A packet with a next hop that is a local address can cause a stack overflow. NVD scores it 7.5, High. The advisory lists version 4.9 and earlier and points to pull request 2264.

What's affected

The GitHub advisory GHSA-7p75-mf53-ffwm lists Contiki-NG version 4.9 and earlier as affected. At the time of the advisory no patched release existed, and it said the fix was expected in the next release. It rates the issue High and gives no numeric score. NVD scores it 7.5, High, so the two agree.

Because the NVD entry was published well after the advisory, check the Contiki-NG releases page and repository for a release that includes the change from pull request 2264. I could not confirm a fixed release number.

The issue affects the IPv6 stack when it processes source routing headers from the RPL protocol implementations.

How to check if you're exposed

Find out whether your firmware builds on Contiki-NG. Look for contiki-ng as a git submodule, a vendored directory or a dependency in your build files. Then check which tag or commit it points to:

git submodule status
git -C path/to/contiki-ng describe --tags

If the version is 4.9 or earlier and does not contain the change from pull request 2264, your devices are in scope. Embedded builds often pin an old commit, so check the commit and not only the product's marketing version.

What to do now

  1. Apply the patch from pull request 2264 to your Contiki-NG copy, or update to a release that includes it once you have confirmed that in the release notes.
  2. Rebuild and test the firmware, then plan an over-the-air or on-site update for deployed devices.
  3. The advisory says there are no known workarounds, so network controls are your stopgap. Keep untrusted hosts from sending IPv6 packets to the devices.
  4. Record which products in your portfolio include Contiki-NG and which version each uses.
  5. Run a dependency scan of your repositories to find vendored copies you did not know about.

Why it matters

The record classes the flaw as CWE-674 (Uncontrolled Recursion). The IPv6 code processes source routing headers and does not validate the resulting next hop address. When the address is local, the function that sends the packet can end up calling itself repeatedly. Each call uses stack memory, and on a small device the stack is small, so it overflows.

The effect on a constrained device is a crash or reboot. For a sensor network that is a loss of availability, and an attacker who can send packets repeatedly can keep it down. The advisory applies to attackers who can send IPv6 packets to the host.

Embedded operating systems are hard to patch for a practical reason. The fix has to be built into new firmware and delivered to devices that may be in the field for years. That puts the weight on knowing early which of your products contain the affected code. Reachability analysis helps with the same question in application code: is the vulnerable function actually used by your build.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is a patched release confirmed?

Not in what I could verify. The advisory pointed to pull request 2264 and a future release. Check the project's releases before relying on a version number.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.