# CVE-2020-19751: Memory corruption in n/a

> A heap-based buffer over-read in GPAC allows attackers to cause denial of service or disclose sensitive memory contents.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 7 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-19751, GHSA-7r87-496h-6jf3, UBUNTU-CVE-2020-19751

## What is CVE-2020-19751?

CVE-2020-19751 is a critical memory corruption vulnerability in Gpac Gpac, published on 7 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in gpac 0.8.0. The gf_odf_del_ipmp_tool function in odf_code.c has a heap-based buffer over-read.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-19751?

It affects 1 product.


Products: Gpac Gpac.

## How do I fix CVE-2020-19751?

Upgrade to a fixed version.

## Is CVE-2020-19751 being exploited?

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

## 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-2020-19751 and fix it if it is affected.

What it is: CVE-2020-19751 is a critical memory corruption vulnerability in Gpac Gpac, published on 7 Sep 2021. 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-2020-19751 in the wild and no public exploit code.

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-2020-19751/ (Markdown: https://insights.sbomify.com/CVE-2020-19751/index.md)
```

## Sources

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

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