Heap corruption via unchecked update-sequence writes
Published May 2, 2022 · Updated Aug 4, 2024
Heap-based buffer overflow in ntfsck in NTFS-3G 2021.8.22 and earlier allows local users to corrupt heap memory via crafted NTFS metadata. The check_file_record function trusts usa_count after merely reporting a length mismatch, then copies update-sequence values beyond the record buffer. Reachability requires ntfsck to process a malicious NTFS file record; the out-of-bounds writes corrupt adjacent heap data under the utility's privileges.
Summary
What happened
Heap-based buffer overflow in ntfsck in NTFS-3G 2021.8.22 and earlier allows local users to corrupt heap memory via crafted NTFS metadata. The check_file_record function trusts usa_count after merely reporting a length mismatch, then copies update-sequence values beyond the record buffer. Reachability requires ntfsck to process a malicious NTFS file record; the out-of-bounds writes corrupt adjacent heap data under the utility's privileges.
The record
- CVE
- CVE-2021-46790
- Published
- May 2, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 2, 2022CVE 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
Public exploit references
- Heap overflow in ntfsckproof of concept · unverified
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