Heap corruption via oversized filename entry set
Published Oct 28, 2023 · Updated Sep 5, 2024
Out-of-bounds write in exfatprogs before 1.2.2 allows local users to corrupt heap memory by checking a crafted exFAT image. The read_file_dentry_set loop trusts the attacker-controlled SecondaryCount and copies more than 17 filename entries into a 256-character heap buffer. Exploitation requires local execution of fsck.exfat against the malformed image and corrupts the process heap.
Summary
What happened
Out-of-bounds write in exfatprogs before 1.2.2 allows local users to corrupt heap memory by checking a crafted exFAT image. The read_file_dentry_set loop trusts the attacker-controlled SecondaryCount and copies more than 17 filename entries into a 256-character heap buffer. Exploitation requires local execution of fsck.exfat against the malformed image and corrupts the process heap.
The record
- CVE
- CVE-2023-45897
- Published
- Oct 28, 2023
- Updated
- Sep 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2023CVE publishedPublication date reported by the CVE source.
- Sep 5, 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