Service crash via malformed PUBLISH packet parsing
Published Jun 8, 2023 · Updated Jan 6, 2025
Heap buffer overflow in NanoMQ 0.17.2 allows remote attackers to crash the broker by sending a malformed MQTT PUBLISH packet. The affected receive paths call nni_msg_get_pub_pid() without first rejecting an invalid QoS value or a missing packet identifier, allowing malformed message data to drive an out-of-bounds heap access. Anonymous MQTT access is sufficient when a vulnerable listener is reachable; exploitation interrupts broker availability, with no documented confidentiality or integrity impact.
Summary
What happened
Heap buffer overflow in NanoMQ 0.17.2 allows remote attackers to crash the broker by sending a malformed MQTT PUBLISH packet. The affected receive paths call nni_msg_get_pub_pid() without first rejecting an invalid QoS value or a missing packet identifier, allowing malformed message data to drive an out-of-bounds heap access. Anonymous MQTT access is sufficient when a vulnerable listener is reachable; exploitation interrupts broker availability, with no documented confidentiality or integrity impact.
The record
- CVE
- CVE-2023-33658
- Published
- Jun 8, 2023
- Updated
- Jan 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 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.
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