Broker crash via unhandled CONNECT null reference
Published Oct 15, 2024 · Updated Apr 3, 2026
Denial of service in the KMQTT 0.2.7 broker allows remote attackers to crash the process with a crafted MQTT CONNECT packet. CONNECT packet handling dereferences a null reference without handling the resulting exception, immediately terminating the broker process. No authentication or user interaction is required, and the reported consequence is limited to loss of broker availability.
Summary
What happened
Denial of service in the KMQTT 0.2.7 broker allows remote attackers to crash the process with a crafted MQTT CONNECT packet. CONNECT packet handling dereferences a null reference without handling the resulting exception, immediately terminating the broker process. No authentication or user interaction is required, and the reported consequence is limited to loss of broker availability.
The record
- CVE
- CVE-2024-44775
- Published
- Oct 15, 2024
- Updated
- Apr 3, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2024CVE publishedPublication date reported by the CVE source.
- Apr 3, 2026Record 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
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