Heap corruption via unchecked Read byte count
Published Apr 11, 2021 · Updated Aug 3, 2024
Buffer overflow in the Rust standard library before 1.50.0 allows attackers to corrupt heap memory through a malicious Read implementation. The read_to_end_with_reservation function adds the byte count returned by Read directly to a Vec length without verifying that the count fits the supplied slice. Triggering the flaw requires a Read implementation to report too many bytes; the published demonstration ends in a process crash from heap corruption.
Summary
What happened
Buffer overflow in the Rust standard library before 1.50.0 allows attackers to corrupt heap memory through a malicious Read implementation. The read_to_end_with_reservation function adds the byte count returned by Read directly to a Vec length without verifying that the count fits the supplied slice. Triggering the flaw requires a Read implementation to report too many bytes; the published demonstration ends in a process crash from heap corruption.
The record
- CVE
- CVE-2021-28875
- Published
- Apr 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-252
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 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.
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
- read_to_end_with_reservation crash demonstrationproof 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