Memory corruption via triggered-topic array overflow
Published Jul 1, 2021 · Updated Aug 4, 2024
Stack-based buffer overflow in uWebSockets 18.11.0 and 18.12.0 allows remote attackers to corrupt memory via MQTT wildcard use. TopicTree queues triggered-topic pointers in a fixed 64-entry array but checks its limit only at function entry, so one publish matching too many wildcards writes past the array. Reachability requires exposed pub/sub behavior and more than 64 triggered wildcard topics; the vendor disputes the issue's security significance.
Summary
What happened
Stack-based buffer overflow in uWebSockets 18.11.0 and 18.12.0 allows remote attackers to corrupt memory via MQTT wildcard use. TopicTree queues triggered-topic pointers in a fixed 64-entry array but checks its limit only at function entry, so one publish matching too many wildcards writes past the array. Reachability requires exposed pub/sub behavior and more than 64 triggered wildcard topics; the vendor disputes the issue's security significance.
The record
- CVE
- CVE-2020-36406
- Published
- Jul 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 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?
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