Daemon crash via unbounded persistent sessions
Published Jun 12, 2024 · Updated Apr 3, 2026
Denial of service in RMQTT Broker 0.4.0 allows remote attackers to exhaust memory and crash the daemon through long-lived MQTT sessions. The MQTT 5 handshake copies the client-supplied session expiry interval into broker state instead of applying the server fitter's configured expiry, allowing attacker-created publish/subscribe sessions to persist. Unauthenticated network access to the MQTT listener is sufficient; enough maintained sessions consume memory until the broker crashes.
Summary
What happened
Denial of service in RMQTT Broker 0.4.0 allows remote attackers to exhaust memory and crash the daemon through long-lived MQTT sessions. The MQTT 5 handshake copies the client-supplied session expiry interval into broker state instead of applying the server fitter's configured expiry, allowing attacker-created publish/subscribe sessions to persist. Unauthenticated network access to the MQTT listener is sufficient; enough maintained sessions consume memory until the broker crashes.
The record
- CVE
- CVE-2024-36856
- Published
- Jun 12, 2024
- Updated
- Apr 3, 2026
- Vendor
- RMQTT
- Product
- RMQTT
- Classifications
- CWE-404, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 12, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.4.0
What conditions does exploitation require?
What is affected?
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
- RMQTT Broker denial-of-service proof of conceptproof 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