# CVE-2018-12713: Race condition in n/a

> Attackers can exploit a race condition in GIMP's temporary file handling to overwrite files or read private content.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-12713, GHSA-hcxp-87ww-ww9m, UBUNTU-CVE-2018-12713

## What is CVE-2018-12713?

CVE-2018-12713 is a critical vulnerability in Gimp Gimp, published on 24 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demonstrated by the gimp_write_and_read_file function in app/tests/test-xcf.c. This might be leveraged by attackers to overwrite files or read file content that was intended to be private.

## Which versions are affected by CVE-2018-12713?

It affects 1 product.


Products: Gimp Gimp.

## How do I fix CVE-2018-12713?

Upgrade to a fixed version.

## Is CVE-2018-12713 being exploited?

There is no known exploitation of CVE-2018-12713 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-2018-12713 and fix it if it is affected.

What it is: CVE-2018-12713 is a critical vulnerability in Gimp Gimp, published on 24 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12713 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-2018-12713/ (Markdown: https://insights.sbomify.com/CVE-2018-12713/index.md)
```

## Sources

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

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