REDHAT-BUG-2562716: Buffer Overflow
Summary: Possible buffer overrun when parsing malicious PNG files with non-standard iCCP chunk Requirements to exploit: A manipulated PNG file with a iCCP chunk that doesn't follow the PNG specification Component affected: Eye of GNOME (eog) Version affected: 2.23.1 <= eog <= 50.3 Patch available: Yes, https://gitlab.gnome.org/GNOME/eog/-/commit/04e4f313421eacb9fc529781542bb7fb81a3cd1a Version fixed (if any already): 50.4 Upstream coordination: See issue report (below) CVSS (optional): Impact (optional): Embargo: No Acknowledgment: PoC script by Ege BALCI Steps to reproduce if available: see issue report Mitigation if available: None Original report:
See https://gitlab.gnome.org/GNOME/eog/-/issues/342#note2903549
This was noticed while verifiying the fix for CVE-2026-107651. The PoC script accompanying that CVE produces PNG files which don't start their iCCP chunks with a NULL-terminated profile name, as mandated by the PNG specification. Intead the chunk us only filled with 'A'.
Once Eye of GNOME loads one of these files it will try to extract the ICC profile from the PNG files. For that it calls eogmetadatareaderpnggeticcprofile() the code tries to skip over the profile name, by walking over the chunk data looking for the first NULL byte. Since it doesn't keep track of the chunk's size it will eventually read past the allocated chunk data.
This is so far only reproducible in ASan enabled builds, in normal builds it seems to "find" a NULL-byte directly after the chunk data.
The issue was fixed already in release 50.4 using the patch linked above
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Eye of GNOME (eog)to a version that resolves this vulnerability.Fixed in 50.4
Event History
Frequently Asked Questions
Which Eye of GNOME versions need to be updated?
Versions from 2.23.1 through 50.3 are affected. Version 50.4 is identified as fixed.
Who is exposed to this issue?
Users of affected Eye of GNOME versions are exposed when the application loads a manipulated PNG containing a non-conformant iCCP chunk. The issue occurs during ICC profile extraction from the image.
Is there an interim mitigation if updating is not immediately possible?
No mitigation is listed. Until an update can be applied, avoid loading untrusted PNG files with the affected application.