# CVE-2022-32990: Denial of service in n/a

> Attackers can cause a denial of service in GIMP by tricking users into opening a crafted XCF file, triggering an unhandled exception.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-32990, GHSA-fj77-3fg4-77vh, MGASA-2022-0330, SUSE-SU-2022:2867-1, SUSE-SU-2022:3106-1, SUSE-SU-2022:3107-1, UBUNTU-CVE-2022-32990

## What is CVE-2022-32990?

CVE-2022-32990 is a medium-severity denial of service vulnerability in Gimp Gimp, published on 24 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue in gimp_layer_invalidate_boundary of GNOME GIMP 2.10.30 allows attackers to trigger an unhandled exception via a crafted XCF file, causing a Denial of Service (DoS).

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2022-32990?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gimp` | SUSE:Linux Enterprise Module for Package Hub 15 SP3 | All versions | 2.10.12-150300.9.6.1 |
| `gimp` | SUSE:Linux Enterprise Module for Package Hub 15 SP4 | All versions | 2.10.30-150400.3.6.2 |
| `gimp` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.8.18-9.24.1 |
| `gimp` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 2.8.18-9.24.1 |
| `gimp` | SUSE:Linux Enterprise Workstation Extension 15 SP3 | All versions | 2.10.12-150300.9.6.1 |
| `gimp` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 2.10.30-150400.3.6.2 |
| `gimp` | openSUSE:Leap 15.3 | All versions | 2.10.12-150300.9.6.1 |
| `gimp` | openSUSE:Leap 15.4 | All versions | 2.10.30-150400.3.6.2 |

Products: Gimp Gimp.

## How do I fix CVE-2022-32990?

Apply the vendor's patch.

## Is CVE-2022-32990 being exploited?

There is no known exploitation of CVE-2022-32990 in the wild and no public exploit code.

## Other vulnerabilities in Gimp Gimp

- [CVE-2010-4541](https://insights.sbomify.com/CVE-2010-4541/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3909](https://insights.sbomify.com/CVE-2009-3909/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-1570](https://insights.sbomify.com/CVE-2009-1570/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-0723](https://insights.sbomify.com/CVE-2009-0723/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-0733](https://insights.sbomify.com/CVE-2009-0733/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32990 and fix it if it is affected.

What it is: CVE-2022-32990 is a medium-severity denial of service vulnerability in Gimp Gimp, published on 24 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-32990 in the wild and no public exploit code.

Affected product: Gimp Gimp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-32990/ (Markdown: https://insights.sbomify.com/CVE-2022-32990/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32990
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32990
- OSV: https://osv.dev/vulnerability/CVE-2022-32990

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-32990/
Summaries are generated and may contain mistakes; the official description above is the record.