Broker crash via pipe-reaper use-after-free race
Published Jun 12, 2023 · Updated Jan 3, 2025
Heap use-after-free in NanoMQ 0.16.5 allows remote attackers to crash its MQTT broker by sending malformed messages. The nano_ctx_send function in nmq_mqtt.c reads a pipe object while reap_worker can free that object through pipe_destroy, causing the sending thread to dereference freed heap memory. No authentication is required to submit the malformed network traffic, and successful triggering aborts the broker process and interrupts service for connected clients.
Summary
What happened
Heap use-after-free in NanoMQ 0.16.5 allows remote attackers to crash its MQTT broker by sending malformed messages. The nano_ctx_send function in nmq_mqtt.c reads a pipe object while reap_worker can free that object through pipe_destroy, causing the sending thread to dereference freed heap memory. No authentication is required to submit the malformed network traffic, and successful triggering aborts the broker process and interrupts service for connected clients.
The record
- CVE
- CVE-2023-34494
- Published
- Jun 12, 2023
- Updated
- Jan 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 12, 2023CVE publishedPublication date reported by the CVE source.
- Jan 3, 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
- Upstream pipe-reaper race 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