Broker denial of service via quadratic property checks
Published Dec 1, 2021 · Updated Aug 4, 2024
Resource exhaustion in Eclipse Mosquitto 1.6 through 2.0.11 allows remote attackers to interrupt broker service via an MQTT v5 CONNECT packet. The mosquitto_property_check_all function compares each property with later entries even for repeatable User Properties, producing quadratic CPU work on a long list. A network-reachable MQTT v5 listener is sufficient, and the bounded consequence is CPU exhaustion that delays or denies broker service without data access or modification.
Summary
What happened
Resource exhaustion in Eclipse Mosquitto 1.6 through 2.0.11 allows remote attackers to interrupt broker service via an MQTT v5 CONNECT packet. The mosquitto_property_check_all function compares each property with later entries even for repeatable User Properties, producing quadratic CPU work on a long list. A network-reachable MQTT v5 listener is sufficient, and the bounded consequence is CPU exhaustion that delays or denies broker service without data access or modification.
The record
- CVE
- CVE-2021-41039
- Published
- Dec 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Eclipse Foundation
- Product
- Eclipse Mosquitto
- Classifications
- CWE-1050, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.6 <unspecified
- Affected versionversion=unspecified <=2.0.11
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.
Weakness, pattern, technique
Public exploit references
- Upstream MQTT v5 User Property performance testproof of concept · validated
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