Incorrect FixVec length via partial read
Published Dec 26, 2021 · Updated Aug 4, 2024
A data-validation flaw in the molecule crate before 0.7.2 allows attackers to obtain an incorrect FixVec length through partial reads. The total_size function computes the length of a partially read FixVec incorrectly, returning a result that can mislead callers about serialized data boundaries. Exploitation requires code that uses total_size on attacker-influenced or malformed partial input; the documented consequence is incorrect parsing behavior rather than a demonstrated confidentiality or integrity compromise.
Summary
What happened
A data-validation flaw in the molecule crate before 0.7.2 allows attackers to obtain an incorrect FixVec length through partial reads. The total_size function computes the length of a partially read FixVec incorrectly, returning a result that can mislead callers about serialized data boundaries. Exploitation requires code that uses total_size on attacker-influenced or malformed partial input; the documented consequence is incorrect parsing behavior rather than a demonstrated confidentiality or integrity compromise.
The record
- CVE
- CVE-2021-45697
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
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.
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
No sourced classifications are available.
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