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

> A memory leak in MPlayer allows attackers to cause a denial of service by exhausting system memory.

- **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:** 15 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-38600, GHSA-26gf-57vw-hc28, UBUNTU-CVE-2022-38600

## What is CVE-2022-38600?

CVE-2022-38600 is a medium-severity denial of service vulnerability in n/a, published on 15 Sep 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

Mplayer SVN-r38374-13.0.1 is vulnerable to Memory Leak via vf.c and vf_vo.c.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Mplayerhq Mplayer.

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

Upgrade to a fixed version.

## Is CVE-2022-38600 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32317](https://insights.sbomify.com/CVE-2022-32317/): Use after free in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38600 is a medium-severity denial of service vulnerability in n/a, published on 15 Sep 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-38600 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-38600/ (Markdown: https://insights.sbomify.com/CVE-2022-38600/index.md)
```

## Sources

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

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