dbcve.org
GimpApplication

CVE-2023-44443

HIGH · 7.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 2.10.36 or later.
See remediation →
81/100
Remediation priority · High
High EPSS No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GIMP PSP File Parsing Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of PSP files. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of the current process. . Was ZDI-CAN-22096.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow vulnerability in GIMP's PSP file parser due to lack of proper validation of user-supplied data during file parsing. The overflow occurs before a memory write operation, allowing attackers to achieve arbitrary code execution in the context of the current process by tricking users into opening malicious PSP files.

MitigationAvoid opening untrusted PSP files in GIMP until an official patch is released. Consider running GIMP in isolated environments or using file sandboxing for untrusted inputs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GimpApplication
Affected:< 2.10.36

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if GIMP is installed
    Run 'gimp --version' or 'gimp -v' in a terminal. On Windows, right-click the GIMP executable, select Properties, and check the File Version tab.
    Affected if GIMP is installed and responds to version query
  2. Determine the installed GIMP version number
    Parse the version output from the previous step. On Linux, also try 'dpkg -l | grep gimp' or 'rpm -qa | grep gimp' to confirm the package version.
    Affected if A version number is returned that is lower than 2.10.36
  3. Confirm PSP file support is present
    Attempt to open a PSP file in GIMP or check if the PSP file format is listed in GIMP's supported formats (Help > About > Supported File Formats).
    Affected if PSP format is supported, indicating the vulnerable parser code is present

If GIMP version is installed and is less than 2.10.36, the PSP file parser contains the integer overflow vulnerability and the user is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.36 or later
Fixed in 2.10.36
Interim mitigation

Avoid opening untrusted PSP files in GIMP until an official patch is released. Consider running GIMP in isolated environments or using file sandboxing for untrusted inputs.

Recommended fix High confidence

GIMP 2.10.36

  1. Check your current GIMP version by opening GIMP and going to Help > About, or by running 'gimp --version' from command line
  2. Download GIMP version 2.10.36 or later from the official GIMP website (www.gimp.org) or your distribution's package manager
  3. If using the official installer, uninstall the current version before installing the new version
  4. If using a package manager (Linux), run the appropriate update command (e.g., 'sudo apt-get update && sudo apt-get install gimp' for Debian/Ubuntu, or 'sudo dnf upgrade gimp' for Fedora)
  5. Restart GIMP after upgrading and verify the version shows 2.10.36 or higher under Help > About
Caveat Point releases typically have minimal breaking changes; however, custom plugins or scripts may need verification for compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gimp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-44443 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data