Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-17784

gimp: Heap-based buffer over-read in load_image function in plug-ins/common/file-gbr.c

Overview

Published
20 Dec 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
8 OS packages
5 Linux distributions
Yes Fix available

Description

In GIMP 2.8.22, there is a heap-based buffer over-read in load_image in plug-ins/common/file-gbr.c in the gbr import parser, related to mishandling of UTF-8 data.

Source: OX vulnerability database

Severity

7.8 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Weakness: CWE-125

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 12 fixes

Red Hat 1 release · 1 package

wont fix 1
gimp
Red Hat fixes for CVE-2017-17784
ReleasePackageFixed in
7 gimp +3 wont fix

SUSE Linux Enterprise 1 release · 1 package

fixed 1
gimp
SUSE Linux Enterprise fixes for CVE-2017-17784
ReleasePackageFixed inAdvisory
12.5 gimp +5 2.8.18-9.18.1 SUSE-SU-2021:0015-1

alpine 4 releases · 1 package

fixed 4
gimp
alpine fixes for CVE-2017-17784
ReleasePackageFixed in
3.22 gimp 2.8.22-r2
3.23 gimp 2.8.22-r2
3.24 gimp 2.8.22-r2
edge gimp 2.8.22-r2

debian 5 releases · 1 package

fixed 5
gimp
debian fixes for CVE-2017-17784
ReleasePackageFixed in
11 gimp 2.8.20-1.1
12 gimp 2.8.20-1.1
13 gimp 2.8.20-1.1
14 gimp 2.8.20-1.1
9 gimp 2.8.18-1+deb9u1

echo 1 release · 1 package

fixed 1
gimp
echo fixes for CVE-2017-17784
ReleasePackageFixed in
gimp 2.8.20-1.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.