Stack corruption via unterminated named-color strings
Published Mar 10, 2026 · Updated Mar 10, 2026
Stack buffer overflow in iccDEV before 2.3.1.5 allows local users to corrupt stack memory or crash iccToXml with a crafted ICC profile. The named-color parser fills fixed-size prefix and suffix arrays without NUL termination, and icFixXml passes them to strcpy, overrunning a 256-byte stack buffer. Processing the attacker-supplied profile requires user interaction; the demonstrated result is an AddressSanitizer-detected crash.
Summary
What happened
Stack buffer overflow in iccDEV before 2.3.1.5 allows local users to corrupt stack memory or crash iccToXml with a crafted ICC profile. The named-color parser fills fixed-size prefix and suffix arrays without NUL termination, and icFixXml passes them to strcpy, overrunning a 256-byte stack buffer. Processing the attacker-supplied profile requires user interaction; the demonstrated result is an AddressSanitizer-detected crash.
The record
- CVE
- CVE-2026-30983
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- International Color Consortium
- Product
- iccDEV
- Classifications
- CWE-120, CWE-121, CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.1.5
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
- sbo-icFixXml-IccUtilXml_cpp-Line314.icc 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