# CVE-2023-29995: Memory corruption in n/a

> A heap overflow in NanoMQ's MQTT parser allows attackers to execute arbitrary code or cause a denial of service.

- **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:** 4 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-6h45-p2j6-r9ph

## What is CVE-2023-29995?

CVE-2023-29995 is a high-severity memory corruption vulnerability in n/a, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In NanoMQ v0.15.0-0, a Heap overflow occurs in copyn_utf8_str function of mqtt_parser.c

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

## Which versions are affected by CVE-2023-29995?

It affects 1 product.


Products: Emqx Nanomq.

## How do I fix CVE-2023-29995?

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

## Is CVE-2023-29995 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29995 exists.

## Other vulnerabilities in n/a

- [CVE-2024-42655](https://insights.sbomify.com/CVE-2024-42655/): Missing authorization in n/a (high 8.8)
- [CVE-2025-59947](https://insights.sbomify.com/CVE-2025-59947/): NanoMQ has Buffer Overflow (high 8.5)
- [CVE-2023-34488](https://insights.sbomify.com/CVE-2023-34488/): Memory corruption in n/a (high 8.0)
- [CVE-2026-32135](https://insights.sbomify.com/CVE-2026-32135/): NanoMQ has Heap Buffer Overflow in URI Parameter Parsing (high 7.7)
- [CVE-2026-36590](https://insights.sbomify.com/CVE-2026-36590/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29995 and fix it if it is affected.

What it is: CVE-2023-29995 is a high-severity memory corruption vulnerability in n/a, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29995 exists.

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-2023-29995/ (Markdown: https://insights.sbomify.com/CVE-2023-29995/index.md)
```

## Sources

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

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