# CVE-2019-9183: Integer overflow in n/a

> An attacker can cause a denial-of-service in Contiki-NG by sending a crafted 6LoWPAN frame that triggers an integer underflow and buffer overflow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p39c-5r3h-6j6m

## What is CVE-2019-9183?

CVE-2019-9183 is a high-severity vulnerability in n/a, published on 23 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Contiki-NG through 4.3 and Contiki through 3.0. A buffer overflow is present due to an integer underflow during 6LoWPAN fragment processing in the face of truncated fragments in os/net/ipv6/sicslowpan.c. This results in accesses of unmapped memory, crashing the application. An attacker can cause a denial-of-service via a crafted 6LoWPAN frame.

Weakness: CWE-787 (Out-of-bounds Write), CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2019-9183?

It affects 2 products.


Products: Contiki-Ng Contiki-Ng, Contiki-Os Contiki.

## How do I fix CVE-2019-9183?

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

## Is CVE-2019-9183 being exploited?

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

## Other vulnerabilities in n/a

- [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-2019-9183 and fix it if it is affected.

What it is: CVE-2019-9183 is a high-severity vulnerability in n/a, published on 23 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9183 in the wild and no public exploit code.

Affected product: n/a. 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-2019-9183/ (Markdown: https://insights.sbomify.com/CVE-2019-9183/index.md)
```

## Sources

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

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