# CVE-2024-0321: Stack-based Buffer Overflow in gpac/gpac

> A stack-based buffer overflow in the GPAC library allows attackers to execute arbitrary code or cause a denial of service.

- **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:** 8 Jan 2024
- **Updated:** 16 May 2025
- **Also known as:** DEBIAN-CVE-2024-0321, GHSA-mf6c-8r47-23j5, UBUNTU-CVE-2024-0321

## What is CVE-2024-0321?

CVE-2024-0321 is a medium-severity memory corruption vulnerability in Gpac Gpac, published on 8 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.3-DEV.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-0321?

It affects 1 product.


Products: Gpac Gpac.

## How do I fix CVE-2024-0321?

Upgrade to a fixed version.

## Is CVE-2024-0321 being exploited?

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

What it is: CVE-2024-0321 is a medium-severity memory corruption vulnerability in Gpac Gpac, published on 8 Jan 2024. 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-2024-0321 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-2024-0321/ (Markdown: https://insights.sbomify.com/CVE-2024-0321/index.md)
```

## Sources

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

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