Memory corruption via allocator-invalid const slice pointer
Published Dec 26, 2021 · Updated Aug 4, 2024
Memory corruption in the vec-const crate before 2.0.0 allows context-dependent attackers to corrupt memory in consuming Rust programs. The crate forges a nonempty Vec from a pointer to a const slice even though Vec ownership requires memory supplied by an allocator. Triggering requires a consuming program to instantiate the affected constant vector; subsequent Vec ownership operations act on memory the allocator does not own.
Summary
What happened
Memory corruption in the vec-const crate before 2.0.0 allows context-dependent attackers to corrupt memory in consuming Rust programs. The crate forges a nonempty Vec from a pointer to a const slice even though Vec ownership requires memory supplied by an allocator. Triggering requires a consuming program to instantiate the affected constant vector; subsequent Vec ownership operations act on memory the allocator does not own.
The record
- CVE
- CVE-2021-45680
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 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.
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