Broker crash via UTF-8 parser over-read
Published May 4, 2023 · Updated Jan 29, 2025
Heap-buffer overflow in NanoMQ 0.15.0-0 allows remote attackers to crash the MQTT broker with a crafted raw MQTT packet. During TCP connection handling, copyn_utf8_str in mqtt_parser.c reads one byte beyond an 18-byte heap allocation while copying attacker-controlled UTF-8 data. An unauthenticated connection to the MQTT listener is sufficient, and the demonstrated consequence is broker termination rather than data disclosure or modification.
Summary
What happened
Heap-buffer overflow in NanoMQ 0.15.0-0 allows remote attackers to crash the MQTT broker with a crafted raw MQTT packet. During TCP connection handling, copyn_utf8_str in mqtt_parser.c reads one byte beyond an 18-byte heap allocation while copying attacker-controlled UTF-8 data. An unauthenticated connection to the MQTT listener is sufficient, and the demonstrated consequence is broker termination rather than data disclosure or modification.
The record
- CVE
- CVE-2023-29995
- Published
- May 4, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 4, 2023CVE publishedPublication date reported by the CVE source.
- Jan 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.
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.
Public exploit references
- NanoMQ raw MQTT packet crash 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