Code execution via unchecked image-derived read length
Published Jun 1, 2023 · Updated Jan 9, 2025
Heap buffer overflow in erofs-utils 1.6 allows local users to execute arbitrary code when fsck.erofs extracts a crafted EROFS image. erofs_read_one_data in data.c passes dev_read a length derived from an image-controlled inode size without checking it against the heap buffer allocation. Exploitation requires processing the image with fsck.erofs extraction and can corrupt heap metadata in that process.
Summary
What happened
Heap buffer overflow in erofs-utils 1.6 allows local users to execute arbitrary code when fsck.erofs extracts a crafted EROFS image. erofs_read_one_data in data.c passes dev_read a length derived from an image-controlled inode size without checking it against the heap buffer allocation. Exploitation requires processing the image with fsck.erofs extraction and can corrupt heap metadata in that process.
The record
- CVE
- CVE-2023-33552
- Published
- Jun 1, 2023
- Updated
- Jan 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Jan 9, 2025Record 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
- Crafted EROFS image crash proof of conceptproof 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