Process corruption via undersized timestamp buffer
Published Mar 8, 2020 · Updated Aug 4, 2024
Stack buffer overflow in The Sleuth Kit 4.8.0 and earlier allows context-dependent attackers to corrupt its process via a crafted YAFFS image. The yaffsfs_istat function passes a 32-byte timeBuf to tsk_fs_time_to_str, which requires a 128-byte destination, while formatting image timestamps. Processing an attacker-created YAFFS image with abnormally large time values is required, and the overflow can interrupt the forensic-analysis process or corrupt its stack.
Summary
What happened
Stack buffer overflow in The Sleuth Kit 4.8.0 and earlier allows context-dependent attackers to corrupt its process via a crafted YAFFS image. The yaffsfs_istat function passes a 32-byte timeBuf to tsk_fs_time_to_str, which requires a 128-byte destination, while formatting image timestamps. Processing an attacker-created YAFFS image with abnormally large time values is required, and the overflow can interrupt the forensic-analysis process or corrupt its stack.
The record
- CVE
- CVE-2020-10232
- Published
- Mar 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
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.
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