# CVE-2022-38853: Memory corruption in n/a

> A buffer overflow in MPlayer's ASF header parsing allows attackers to execute arbitrary code or cause a crash via malicious media files.

- **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-38853, GHSA-9vv9-973m-jrrx, UBUNTU-CVE-2022-38853

## What is CVE-2022-38853?

CVE-2022-38853 is a medium-severity memory corruption 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

Certain The MPlayer Project products are vulnerable to Buffer Overflow via function asf_init_audio_stream() of libmpdemux/asfheader.c. This affects mplayer SVN-r38374-13.0.1 and mencoder SVN-r38374-13.0.1.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Mplayerhq Mencoder, Mplayerhq Mplayer.

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

Apply the vendor's patch.

## Is CVE-2022-38853 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38862](https://insights.sbomify.com/CVE-2022-38862/): Memory corruption in n/a (high 7.8)
- [CVE-2022-38856](https://insights.sbomify.com/CVE-2022-38856/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38853 is a medium-severity memory corruption 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-38853 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-38853/ (Markdown: https://insights.sbomify.com/CVE-2022-38853/index.md)
```

## Sources

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

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