Arbitrary code execution via unchecked PICT buffer bounds
Published Sep 25, 2023 · Updated Nov 4, 2025
Heap-based buffer overflow in ImageGear 20.1 allows remote attackers to execute arbitrary code by supplying a crafted PICT file. In pictwread, file-controlled bounds size a heap allocation from image height, while an independent file-controlled rowBytes value bounds a later memory copy or fill. An unauthenticated application path that passes attacker-supplied PICT files to the library is sufficient, and the resulting heap corruption executes code in the host process.
Summary
What happened
Heap-based buffer overflow in ImageGear 20.1 allows remote attackers to execute arbitrary code by supplying a crafted PICT file. In pictwread, file-controlled bounds size a heap allocation from image height, while an independent file-controlled rowBytes value bounds a later memory copy or fill. An unauthenticated application path that passes attacker-supplied PICT files to the library is sufficient, and the resulting heap corruption executes code in the host process.
The record
- CVE
- CVE-2023-35002
- Published
- Sep 25, 2023
- Updated
- Nov 4, 2025
- Vendor
- Accusoft
- Product
- ImageGear
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20.1
What conditions does exploitation require?
What is affected?
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
- Cisco Talos crafted PICT reproductionproof 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