# CVE-2019-12219: Use after free in n/a

> An invalid free error in SDL2_image allows attackers to cause denial of service or potentially execute code via crafted image files.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-12219, DEBIAN-CVE-2019-12219, GHSA-rh22-q4j2-m68r, UBUNTU-CVE-2019-12219

## What is CVE-2019-12219?

CVE-2019-12219 is a high-severity use after free vulnerability in n/a, published on 20 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. There is an invalid free error in the SDL function SDL_SetError_REAL at SDL_error.c.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2019-12219?

It affects 2 products.


Products: Libsdl Sdl2 Image, Libsdl Simple Directmedia Layer.

## How do I fix CVE-2019-12219?

Upgrade to a fixed version.

## Is CVE-2019-12219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-5057](https://insights.sbomify.com/CVE-2019-5057/): Memory corruption in SDL (high 8.8)
- [CVE-2019-5058](https://insights.sbomify.com/CVE-2019-5058/): Memory corruption in SDL (high 8.8)
- [CVE-2019-5059](https://insights.sbomify.com/CVE-2019-5059/): Integer overflow in SDL (high 8.8)
- [CVE-2019-5060](https://insights.sbomify.com/CVE-2019-5060/): Integer overflow in SDL (high 8.8)
- [CVE-2019-12217](https://insights.sbomify.com/CVE-2019-12217/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12219 and fix it if it is affected.

What it is: CVE-2019-12219 is a high-severity use after free vulnerability in n/a, published on 20 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12219 in the wild and no public exploit code.

Affected product: n/a. 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-2019-12219/ (Markdown: https://insights.sbomify.com/CVE-2019-12219/index.md)
```

## Sources

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

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