First published: Wed Dec 20 2017(Updated: )
In GIMP 2.8.22, there is a stack-based buffer over-read in xcf_load_stream in app/xcf/xcf.c when there is no '\0' character after the version string.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
ubuntu/gimp | <2.8.10-0ubuntu1.2 | 2.8.10-0ubuntu1.2 |
ubuntu/gimp | <2.8.20-1.1 | 2.8.20-1.1 |
debian/gimp | 2.10.8-2 2.10.8-2+deb10u1 2.10.22-4 2.10.34-1 2.10.36-1 | |
GIMP GIMP | =2.8.22 | |
Debian Debian Linux | =7.0 | |
Debian Debian Linux | =8.0 | |
Debian Debian Linux | =9.0 | |
Canonical Ubuntu Linux | =14.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2017-17788.
The severity of CVE-2017-17788 is medium with a CVSS score of 5.5.
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.
Yes, the following versions of GIMP have been patched: 2.10.8-2, 2.10.22-4, and 2.10.34-1.
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.