# CVE-2021-29978: Multiple low security issues were discovered and fixed in a security audit of Mozilla VPN 2.x branch as part of a 3rd party security audit.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-24c6-8h6m-mfm3

## What is CVE-2021-29978?

CVE-2021-29978 is a critical vulnerability in Mozilla VPN, published on 5 Aug 2021. 

### Official description

Multiple low security issues were discovered and fixed in a security audit of Mozilla VPN 2.x branch as part of a 3rd party security audit. This vulnerability affects Mozilla VPN < 2.3.

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

It affects 1 product.


Products: Mozilla Mozilla Vpn.

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

No fix has been published for CVE-2021-29978 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-29978 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29978 and fix it if it is affected.

What it is: CVE-2021-29978 is a critical vulnerability in Mozilla VPN, published on 5 Aug 2021. 
Exploitation: There is no known exploitation of CVE-2021-29978 in the wild and no public exploit code.

Affected product: Mozilla VPN. 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-29978/ (Markdown: https://insights.sbomify.com/CVE-2021-29978/index.md)
```

## Sources

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

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