Memory corruption via panic-unsafe String retention
Published Apr 11, 2021 · Updated Aug 4, 2024
Memory corruption in the Rust standard library 1.26.0 through 1.48.0 allows attackers to violate UTF-8 invariants via String::retain. String::retain temporarily exposes a partially compacted buffer and fails to restore a valid length when its predicate closure panics, leaving non-UTF-8 bytes in a safe String. Exploitation requires code that supplies a panicking closure and catches the unwind; later String APIs can then trigger memory-safety violations, including out-of-bounds writes.
Summary
What happened
Memory corruption in the Rust standard library 1.26.0 through 1.48.0 allows attackers to violate UTF-8 invariants via String::retain. String::retain temporarily exposes a partially compacted buffer and fails to restore a valid length when its predicate closure panics, leaving non-UTF-8 bytes in a safe String. Exploitation requires code that supplies a panicking closure and catches the unwind; later String APIs can then trigger memory-safety violations, including out-of-bounds writes.
The record
- CVE
- CVE-2020-36317
- Published
- Apr 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 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.
Weakness, pattern, technique
Public exploit references
- Upstream String::retain panic reproducerproof 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