Service interruption via client-controlled connection exhaustion
Published Jun 4, 2020 · Updated Aug 4, 2024
Denial of service in MQTT 3.1.1 allows remote attackers to prevent new broker connections through crafted Keep-Alive values. The CONNECT packet lets a client set a 16-bit Keep-Alive value, requiring the broker to retain each idle connection for 1.5 times that interval. No authentication or user interaction is required; enough concurrent connections exhaust the broker's connection limit and interrupt service.
Summary
What happened
Denial of service in MQTT 3.1.1 allows remote attackers to prevent new broker connections through crafted Keep-Alive values. The CONNECT packet lets a client set a 16-bit Keep-Alive value, requiring the broker to retain each idle connection for 1.5 times that interval. No authentication or user interaction is required; enough concurrent connections exhaust the broker's connection limit and interrupt service.
The record
- CVE
- CVE-2020-13849
- Published
- Jun 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- MQTT_SlowITefunctional · 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