Memory corruption via unchecked network-name length
Published Apr 28, 2020 · Updated Aug 5, 2024
Stack-based buffer overflow in OpenThread before 2019-12-13 allows attackers to write beyond a stack buffer via an oversized network name. MeshCoP::Commissioner::GeneratePskc measures the supplied name with strlen and copies that many bytes into a fixed-size salt buffer without enforcing OT_NETWORK_NAME_MAX_SIZE. The NCP property handler can reach this path during commissioner PSKc generation; public OSS-Fuzz evidence demonstrates an out-of-bounds write but not code execution.
Summary
What happened
Stack-based buffer overflow in OpenThread before 2019-12-13 allows attackers to write beyond a stack buffer via an oversized network name. MeshCoP::Commissioner::GeneratePskc measures the supplied name with strlen and copies that many bytes into a fixed-size salt buffer without enforcing OT_NETWORK_NAME_MAX_SIZE. The NCP property handler can reach this path during commissioner PSKc generation; public OSS-Fuzz evidence demonstrates an out-of-bounds write but not code execution.
The record
- CVE
- CVE-2019-20791
- Published
- Apr 28, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
Weakness, pattern, technique
Public exploit references
- OSS-Fuzz issue 19386proof 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