# CVE-2024-42648: Memory corruption in n/a

> Attackers can cause a Denial of Service in NanoMQ by sending a crafted CONNECT message that triggers a heap overflow.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2025
- **Updated:** 16 Jul 2025
- **Also known as:** GHSA-rc57-p94g-3jpv

## What is CVE-2024-42648?

CVE-2024-42648 is a medium-severity memory corruption vulnerability in n/a, published on 14 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

NanoMQ v0.22.10 was discovered to contain a heap overflow which allows attackers to cause a Denial of Service (DoS) via a crafted CONNECT message.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-42648?

It affects 1 product.


Products: Emqx Nanomq.

## How do I fix CVE-2024-42648?

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

## Is CVE-2024-42648 being exploited?

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

## 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-2024-42648 and fix it if it is affected.

What it is: CVE-2024-42648 is a medium-severity memory corruption vulnerability in n/a, published on 14 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-42648 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-2024-42648/ (Markdown: https://insights.sbomify.com/CVE-2024-42648/index.md)
```

## Sources

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

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