# CVE-2018-20579: Memory corruption in n/a

> A stack-based buffer overflow in Contiki-NG's JSON parser allows attackers to cause out-of-bounds writes, potentially leading to code execution or crashes.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r9mc-297w-w563

## What is CVE-2018-20579?

CVE-2018-20579 is a high-severity memory corruption vulnerability in n/a, published on 28 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Contiki-NG before 4.2 has a stack-based buffer overflow in the push function in os/lib/json/jsonparse.c that allows an out-of-bounds write of an '{' or '[' character.

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

## Which versions are affected by CVE-2018-20579?

It affects 1 product.


Products: Contiki-Ng Project Contiki-Ng.

## How do I fix CVE-2018-20579?

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

## Is CVE-2018-20579 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20579 and fix it if it is affected.

What it is: CVE-2018-20579 is a high-severity memory corruption vulnerability in n/a, published on 28 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20579 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-2018-20579/ (Markdown: https://insights.sbomify.com/CVE-2018-20579/index.md)
```

## Sources

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

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