# CVE-2024-39792: NGINX Plus MQTT vulnerability

> Attackers can cause memory exhaustion in NGINX Plus when the MQTT pre-read module is enabled, leading to denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2024
- **Updated:** 15 Aug 2024
- **Also known as:** GHSA-j72m-4pgw-w3qv

## What is CVE-2024-39792?

CVE-2024-39792 is a high-severity denial of service vulnerability in F5 NGINX Plus, published on 14 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When the NGINX Plus is configured to use the MQTT pre-read module, undisclosed requests can cause an increase in memory resource utilization.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release), CWE-825 (Expired Pointer Dereference)

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

It affects 1 product.


Products: F5 Nginx Plus.

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

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

## Is CVE-2024-39792 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39792 and fix it if it is affected.

What it is: CVE-2024-39792 is a high-severity denial of service vulnerability in F5 NGINX Plus, published on 14 Aug 2024. 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-2024-39792 in the wild and no public exploit code.

Affected product: F5 NGINX Plus. 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-39792/ (Markdown: https://insights.sbomify.com/CVE-2024-39792/index.md)
```

## Sources

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

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