# CVE-2022-47660: Integer overflow in n/a

> An integer overflow in GPAC MP4Box allows attackers to cause a denial of service via crafted media files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-47660, GHSA-29x4-r4w3-f8r9, UBUNTU-CVE-2022-47660

## What is CVE-2022-47660?

CVE-2022-47660 is a high-severity vulnerability in Gpac Gpac, published on 5 Jan 2023. 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

GPAC MP4Box 2.1-DEV-rev644-g5c4df2a67 is has an integer overflow in isomedia/isom_write.c

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Gpac Gpac.

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

Upgrade to a fixed version.

## Is CVE-2022-47660 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47660 exists.

## Other vulnerabilities in Gpac Gpac

- [CVE-2023-46427](https://insights.sbomify.com/CVE-2023-46427/): Null dereference in n/a (critical 9.8)
- [CVE-2023-46932](https://insights.sbomify.com/CVE-2023-46932/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-36190](https://insights.sbomify.com/CVE-2022-36190/): Use after free in n/a (critical 9.8)
- [CVE-2021-28300](https://insights.sbomify.com/CVE-2021-28300/): Null dereference in n/a (critical 9.8)
- [CVE-2020-11558](https://insights.sbomify.com/CVE-2020-11558/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47660 is a high-severity vulnerability in Gpac Gpac, published on 5 Jan 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47660 exists.

Affected product: Gpac Gpac. 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-47660/ (Markdown: https://insights.sbomify.com/CVE-2022-47660/index.md)
```

## Sources

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

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