# CVE-2021-30015: Null dereference in n/a

> A null pointer dereference in GPAC allows attackers to cause a denial of service via crafted media files.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-30015, GHSA-6cf9-gr3m-fgc8, UBUNTU-CVE-2021-30015

## What is CVE-2021-30015?

CVE-2021-30015 is a medium-severity vulnerability in Gpac Gpac, published on 19 Apr 2021. 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

There is a Null Pointer Dereference in function filter_core/filter_pck.c:gf_filter_pck_new_alloc_internal in GPAC 1.0.1. The pid comes from function av1dmx_parse_flush_sample, the ctx.opid maybe NULL. The result is a crash in gf_filter_pck_new_alloc_internal.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2021-30015?

It affects 1 product.


Products: Gpac Gpac.

## How do I fix CVE-2021-30015?

Apply the vendor's patch.

## Is CVE-2021-30015 being exploited?

There is no known exploitation of CVE-2021-30015 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-2021-30015 and fix it if it is affected.

What it is: CVE-2021-30015 is a medium-severity vulnerability in Gpac Gpac, published on 19 Apr 2021. 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: There is no known exploitation of CVE-2021-30015 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-2021-30015/ (Markdown: https://insights.sbomify.com/CVE-2021-30015/index.md)
```

## Sources

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

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