Nginx PlusWeb server / proxy · F5
CVE-2024-39792
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceWhen NGINX Plus is configured to use the MQTT pre-read module, certain undisclosed MQTT requests can trigger excessive memory consumption, leading to potential denial of service through memory resource exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nginx PlusWeb server / proxy
= r30= r31= r32CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check NGINX Plus versionRun 'nginx -v' or 'nginx -V 2>&1' to display the version information. Alternatively, check /etc/os-release for nginx-plus package version.Affected if The version displayed is r30, r31, or r32.
-
Verify MQTT pre-read module is loadedRun 'nginx -V 2>&1' and look for 'ngx_stream_mqtt_preread_module' in the compiled modules list.Affected if The ngx_stream_mqtt_preread_module appears in the loaded modules.
-
Inspect NGINX configuration for MQTT pre-read usageSearch configuration files (typically in /etc/nginx/ or /etc/nginx/conf.d/) for 'mqtt_preread on;' directive within stream blocks.Affected if The directive 'mqtt_preread on;' is found and enabled in any stream block.
-
Confirm stream block with MQTT is activeCheck that the stream block containing 'mqtt_preread on;' is not commented out and is included in the main nginx.conf via 'include' directives.Affected if An active (non-commented) stream block contains the mqtt_preread directive.
The environment is affected if NGINX Plus r30, r31, or r32 is running with the MQTT pre-read module (mqtt_preread on) configured and enabled in an active stream block.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the MQTT pre-read module configuration in NGINX Plus until an official patch is available; consider implementing rate limiting as a compensating control.
Fix this in Nginx Plus
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data