# CVE-2022-34568: Use after free in n/a

> A use-after-free vulnerability in SDL v1.2 allows attackers to execute arbitrary code or cause denial of service via the XFree function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** AZL-43786, DEBIAN-CVE-2022-34568, GHSA-wr7h-5wm3-p3h4, UBUNTU-CVE-2022-34568, USN-5586-1

## What is CVE-2022-34568?

CVE-2022-34568 is a high-severity use after free vulnerability in n/a, published on 28 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SDL v1.2 was discovered to contain a use-after-free via the XFree function at /src/video/x11/SDL_x11yuv.c.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Libsdl Simple Directmedia Layer.

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

Apply the vendor's patch.

## Is CVE-2022-34568 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-33657](https://insights.sbomify.com/CVE-2021-33657/): Memory corruption in SDL2 (high 8.8)
- [CVE-2019-14906](https://insights.sbomify.com/CVE-2019-14906/): Memory corruption in SDL (high 8.1)
- [CVE-2022-4743](https://insights.sbomify.com/CVE-2022-4743/): Denial of service in SDL2 (high 7.5)
- [CVE-2019-12222](https://insights.sbomify.com/CVE-2019-12222/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34568 is a high-severity use after free vulnerability in n/a, published on 28 Jul 2022. 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-2022-34568 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-2022-34568/ (Markdown: https://insights.sbomify.com/CVE-2022-34568/index.md)
```

## Sources

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

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