Process crash via zero PICT pixel size
Published Apr 14, 2021 · Updated Jan 26, 2026
Divide-by-zero in Deark before 1.5.8 allows context-dependent attackers to crash the process via a crafted PICT file. The PICT pixmap parser's fmtutil_macbitmap_read_pixmap_only_fields function divides rowbytes times eight by an unchecked pixelsize that can be zero. The file must be opened or processed by Deark, and successful exploitation terminates that Deark process without reading or modifying data.
Summary
What happened
Divide-by-zero in Deark before 1.5.8 allows context-dependent attackers to crash the process via a crafted PICT file. The PICT pixmap parser's fmtutil_macbitmap_read_pixmap_only_fields function divides rowbytes times eight by an unchecked pixelsize that can be zero. The file must be opened or processed by Deark, and successful exploitation terminates that Deark process without reading or modifying data.
The record
- CVE
- CVE-2021-28856
- Published
- Apr 14, 2021
- Updated
- Jan 26, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-369, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2021CVE publishedPublication date reported by the CVE source.
- Jan 26, 2026Record 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
- Crafted PICT file 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