Denial of service via unreleased PUBLISH allocations
Published Jul 14, 2025 · Updated Jul 16, 2025
Memory leak in EMQX NanoMQ 0.22.10 allows remote attackers to exhaust broker memory via crafted MQTT PUBLISH messages. The broker's PUBLISH-message processing allocates heap memory for malformed packet data but never releases the allocation. Unauthenticated MQTT access permits repeated triggering, progressively consuming memory until the broker service is interrupted.
Summary
What happened
Memory leak in EMQX NanoMQ 0.22.10 allows remote attackers to exhaust broker memory via crafted MQTT PUBLISH messages. The broker's PUBLISH-message processing allocates heap memory for malformed packet data but never releases the allocation. Unauthenticated MQTT access permits repeated triggering, progressively consuming memory until the broker service is interrupted.
The record
- CVE
- CVE-2024-42649
- Published
- Jul 14, 2025
- Updated
- Jul 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2025CVE publishedPublication date reported by the CVE source.
- Jul 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted MQTT PUBLISH message proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo