# CVE-2022-36054: Out-of-bounds write when decompressing 6LoWPAN payload in Contiki-NG

> An attacker can trigger an out-of-bounds write in Contiki-NG by sending crafted 6LoWPAN packets, potentially leading to code execution or system crashes.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-c36p-vhwg-244c

## What is CVE-2022-36054?

CVE-2022-36054 is a medium-severity memory corruption vulnerability in contiki-ng, published on 1 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Contiki-NG is an open-source, cross-platform operating system for Next-Generation IoT devices. The 6LoWPAN implementation in the Contiki-NG operating system (file os/net/ipv6/sicslowpan.c) contains an input function that processes incoming packets and copies them into a packet buffer. Because of a missing length check in the input function, it is possible to write outside the packet buffer's boundary. The vulnerability can be exploited by anyone who has the possibility to send 6LoWPAN packets to a Contiki-NG system. In particular, the vulnerability is exposed when sending either of two types of 6LoWPAN packets: an unfragmented packet or the first fragment of a fragmented packet. If the packet is sufficiently large, a subsequent memory copy will cause an out-of-bounds write with data supplied by the attacker.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-36054?

It affects 1 product.


Products: Contiki-Ng Contiki-Ng.

## How do I fix CVE-2022-36054?

No fix has been published for CVE-2022-36054 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-36054 being exploited?

There is no known exploitation of CVE-2022-36054 in the wild and no public exploit code.

## Other vulnerabilities in contiki-ng

- [CVE-2018-19417](https://insights.sbomify.com/CVE-2018-19417/): Memory corruption in n/a (critical 10.0)
- [CVE-2023-30546](https://insights.sbomify.com/CVE-2023-30546/): Contiki-NG has off-by-one error in Antelope DBMS (critical 9.8)
- [CVE-2020-24336](https://insights.sbomify.com/CVE-2020-24336/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-14934](https://insights.sbomify.com/CVE-2020-14934/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-14935](https://insights.sbomify.com/CVE-2020-14935/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36054 and fix it if it is affected.

What it is: CVE-2022-36054 is a medium-severity memory corruption vulnerability in contiki-ng, published on 1 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36054 in the wild and no public exploit code.

Affected product: contiki-ng. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-36054/ (Markdown: https://insights.sbomify.com/CVE-2022-36054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-36054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-36054
- OSV: https://osv.dev/vulnerability/CVE-2022-36054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-36054/
Summaries are generated and may contain mistakes; the official description above is the record.