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

> A memory corruption vulnerability in the Ittiam libmpeg2 library allows attackers to potentially execute arbitrary code or cause a denial of service via overlapping memory blocks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2pc7-q5qc-x4v8

## What is CVE-2022-37416?

CVE-2022-37416 is a medium-severity memory corruption vulnerability in n/a, published on 5 Aug 2022. 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

Ittiam libmpeg2 before 2022-07-27 uses memcpy with overlapping memory blocks in impeg2_mc_fullx_fully_8x8.

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

It affects 1 product.


Products: Ittiam Libmpeg2.

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

No fix has been published for CVE-2022-37416 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-37416 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37416 is a medium-severity memory corruption vulnerability in n/a, published on 5 Aug 2022. 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-2022-37416 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-37416/ (Markdown: https://insights.sbomify.com/CVE-2022-37416/index.md)
```

## Sources

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

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