# CVE-2023-5520: Out-of-bounds Read in gpac/gpac

> An out-of-bounds read in the GPAC library allows attackers to cause denial of service or potentially execute code via crafted media files.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Oct 2023
- **Updated:** 18 Sep 2024
- **Also known as:** DEBIAN-CVE-2023-5520, GHSA-8x9m-4hhm-x696, UBUNTU-CVE-2023-5520

## What is CVE-2023-5520?

CVE-2023-5520 is a medium-severity memory corruption vulnerability in Gpac Gpac, published on 11 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.2.2.

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

## Which versions are affected by CVE-2023-5520?

It affects 1 product.


Products: Gpac Gpac.

## How do I fix CVE-2023-5520?

Upgrade to a fixed version.

## Is CVE-2023-5520 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5520 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-2023-5520 and fix it if it is affected.

What it is: CVE-2023-5520 is a medium-severity memory corruption vulnerability in Gpac Gpac, published on 11 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5520 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-2023-5520/ (Markdown: https://insights.sbomify.com/CVE-2023-5520/index.md)
```

## Sources

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

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