Unauthenticated broker crash via out-of-bounds read
Published Sep 12, 2024 · Updated Oct 30, 2024
Out-of-bounds read in EMQ Technologies NanoMQ 0.21.9 allows remote attackers to crash the MQTT broker through network input. The only technical reference is unavailable, so the specific parser, message type, and incorrect read operation are not publicly documented. No authentication or user interaction is required; successful exploitation interrupts broker service without reported data disclosure or modification.
Summary
What happened
Out-of-bounds read in EMQ Technologies NanoMQ 0.21.9 allows remote attackers to crash the MQTT broker through network input. The only technical reference is unavailable, so the specific parser, message type, and incorrect read operation are not publicly documented. No authentication or user interaction is required; successful exploitation interrupts broker service without reported data disclosure or modification.
The record
- CVE
- CVE-2024-44460
- Published
- Sep 12, 2024
- Updated
- Oct 30, 2024
- Vendor
- EMQ Technologies
- Product
- NanoMQ
- Classifications
- CWE-125, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.21.9
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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