Process-memory disclosure via uninitialized archive bytes
Published Apr 30, 2021 · Updated Aug 3, 2024
Information disclosure in the rkyv crate before 0.6.0 allows remote attackers to read process memory through serialized archives. Archive::resolve writes complete struct-compatible memory into an archive without ensuring that struct padding and unused enum bytes are initialized. Exposure occurs when an application serializes affected types and stores the archive or sends it over an unsecured channel, disclosing residual bytes occupying those gaps.
Summary
What happened
Information disclosure in the rkyv crate before 0.6.0 allows remote attackers to read process memory through serialized archives. Archive::resolve writes complete struct-compatible memory into an archive without ensuring that struct padding and unused enum bytes are initialized. Exposure occurs when an application serializes affected types and stores the archive or sends it over an unsecured channel, disclosing residual bytes occupying those gaps.
The record
- CVE
- CVE-2021-31919
- Published
- Apr 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-772, CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 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