Memory corruption via understated iterator length
Published Apr 1, 2021 · Updated Aug 3, 2024
Out-of-bounds write in the Rust reorder crate before 1.1.0 allows attackers to corrupt memory via an iterator that understates its length. The safe swap_index function allocates a vector from ExactSizeIterator::len(), forms a mutable slice without bounds checks, and indexes that slice for every yielded item. A caller must supply an iterator that yields more elements than its reported length; the resulting write crosses the allocation boundary and corrupts the consuming process's memory.
Summary
What happened
Out-of-bounds write in the Rust reorder crate before 1.1.0 allows attackers to corrupt memory via an iterator that understates its length. The safe swap_index function allocates a vector from ExactSizeIterator::len(), forms a mutable slice without bounds checks, and indexes that slice for every yielded item. A caller must supply an iterator that yields more elements than its reported length; the resulting write crosses the allocation boundary and corrupts the consuming process's memory.
The record
- CVE
- CVE-2021-29941
- Published
- Apr 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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