Client crash via incorrect packet-type matching
Published Dec 31, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in wolfSSL wolfMQTT 1.9 allows context-dependent attackers to crash a client via a crafted MQTT packet. MqttClient_WaitType equates non-publish-response packet types by comparing false results, so the wrong response object reaches MqttDecode_Publish and eight heap bytes are overwritten. The client must process the attacker-controlled packet while waiting for another packet type; the demonstrated consequence is a client crash.
Summary
What happened
Heap-based buffer overflow in wolfSSL wolfMQTT 1.9 allows context-dependent attackers to crash a client via a crafted MQTT packet. MqttClient_WaitType equates non-publish-response packet types by comparing false results, so the wrong response object reaches MqttDecode_Publish and eight heap bytes are overwritten. The client must process the attacker-controlled packet while waiting for another packet type; the demonstrated consequence is a client crash.
The record
- CVE
- CVE-2021-45933
- Published
- Dec 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 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?
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
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