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

> A buffer overflow in the MQTT server allows remote attackers to execute arbitrary code via stack smashing.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cxvc-6cjq-88vx

## What is CVE-2018-19417?

CVE-2018-19417 is a critical memory corruption vulnerability in n/a, published on 21 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the MQTT server in Contiki-NG before 4.2. The function parse_publish_vhdr() that parses MQTT PUBLISH messages with a variable length header uses memcpy to input data into a fixed size buffer. The allocated buffer can fit only MQTT_MAX_TOPIC_LENGTH (default 64) bytes, and a length check is missing. This could lead to Remote Code Execution via a stack-smashing attack (overwriting the function return address). Contiki-NG does not separate the MQTT server from other servers and the OS modules, so access to all memory regions is possible.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Contiki-Ng Contiki-Ng.

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

Upgrade to a fixed version.

## Is CVE-2018-19417 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2020-14936](https://insights.sbomify.com/CVE-2020-14936/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19417 is a critical memory corruption vulnerability in n/a, published on 21 Nov 2018. 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-2018-19417 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-19417/ (Markdown: https://insights.sbomify.com/CVE-2018-19417/index.md)
```

## Sources

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

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