CVE-2017-17788: Medium severity GIMP GIMP vulnerability
In GIMP 2.8.22, there is a stack-based buffer over-read in xcfloadstream in app/xcf/xcf.c when there is no '\0' character after the version string.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/gimpto a version that resolves this vulnerability.Fixed in 2.10.22-4+deb11u2Fixed in 2.10.22-4+deb11u6Fixed in 2.10.34-1+deb12u5Fixed in 2.10.34-1+deb12u8Fixed in 3.0.4-3+deb13u2Fixed in 3.0.4-3+deb13u6Fixed in 3.2.0~RC2-3.1Fixed in 3.2.0~RC2-3.3 - Upgrade
Upgrade
alpine/gimpto a version that resolves this vulnerability.Fixed in 2.8.22-r2
Event History
Frequently Asked Questions
What is the vulnerability ID?
The vulnerability ID is CVE-2017-17788.
What is the severity of CVE-2017-17788?
The severity of CVE-2017-17788 is medium with a CVSS score of 5.5.
How does CVE-2017-17788 impact GIMP?
CVE-2017-17788 can cause a stack-based buffer over-read in GIMP 2.8.22 when there is no '\0' character after the version string.
Is there a fix available for CVE-2017-17788?
Yes, the following versions of GIMP have been patched: 2.10.8-2, 2.10.22-4, and 2.10.34-1.
Where can I find more information about CVE-2017-17788?
You can find more information about CVE-2017-17788 at the following references: http://www.openwall.com/lists/oss-security/2017/12/19/5, https://bugzilla.gnome.org/show_bug.cgi?id=790783, and https://lists.debian.org/debian-lts-announce/2017/12/msg00023.html.