Broker crash via retained-message pointer reuse
Published Jul 29, 2025 · Updated Jul 29, 2025
Heap use-after-free in NanoMQ 0.17.9 allows remote attackers to crash the broker with a crafted multi-topic SUBSCRIBE message. During retained-message matching in sub_Ctx_handle, NanoMQ queues and frees a matching message without clearing its pointer, then reuses the dangling pointer when a later topic matches under rh=1 handling. Network access to the MQTT listener is sufficient; the documented consequence is broker memory corruption and a service crash.
Summary
What happened
Heap use-after-free in NanoMQ 0.17.9 allows remote attackers to crash the broker with a crafted multi-topic SUBSCRIBE message. During retained-message matching in sub_Ctx_handle, NanoMQ queues and frees a matching message without clearing its pointer, then reuses the dangling pointer when a later topic matches under rh=1 handling. Network access to the MQTT listener is sufficient; the documented consequence is broker memory corruption and a service crash.
The record
- CVE
- CVE-2024-42651
- Published
- Jul 29, 2025
- Updated
- Jul 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2025CVE publishedPublication date reported by the CVE source.
- Jul 29, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- NanoMQ retained-message use-after-free reproducerproof 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