CLI crash via undersized NTFS update-array guard
Published Mar 8, 2020 · Updated Aug 4, 2024
Heap-based buffer over-read in The Sleuth Kit 4.8.0 and earlier allows attackers to crash fls by processing a crafted NTFS image. ntfs_dinode_lookup in tsk/fs/ntfs.c validates only the two-byte ntfs_upd structure at the update-sequence offset, ignoring the remaining update array before reading it. The attacker must cause an affected command-line tool to parse the image; the demonstrated consequence is an AddressSanitizer-detected abort, not code execution.
Summary
What happened
Heap-based buffer over-read in The Sleuth Kit 4.8.0 and earlier allows attackers to crash fls by processing a crafted NTFS image. ntfs_dinode_lookup in tsk/fs/ntfs.c validates only the two-byte ntfs_upd structure at the update-sequence offset, ignoring the remaining update array before reading it. The attacker must cause an affected command-line tool to parse the image; the demonstrated consequence is an AddressSanitizer-detected abort, not code execution.
The record
- CVE
- CVE-2020-10233
- Published
- Mar 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 8, 2020CVE 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
- Google AutoFuzz NTFS image reproducerproof 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