# CVE-2020-8116: dot-prop Prototype Pollution vulnerability

> Prototype pollution in dot-prop allows attackers to modify JavaScript object prototypes, potentially leading to code execution or security bypasses.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** AZL-45084, DEBIAN-CVE-2020-8116, GHSA-ff7x-qrg7-qggm, ROOT-APP-NPM-CVE-2020-8116, UBUNTU-CVE-2020-8116

## What is CVE-2020-8116?

CVE-2020-8116 is a high-severity vulnerability in dot-prop, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes), CWE-471 (Modification of Assumed-Immutable Data (MAID))

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

4 open source packages ship an affected version, including dot-prop. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dot-prop` | npm | All versions | 4.2.1 |
| `dot-prop` | npm | All versions | 4.2.1 |
| `dot-prop` | npm | From 5.0.0 | 5.1.1 |
| `dot-prop` | npm | From 5.0.0 | 5.1.1 |

Products: Dot-Prop Project Dot-Prop.

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

Upgrade dot-prop to a fixed version for your release line: 4.2.1 or 5.1.1.

## Is CVE-2020-8116 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8116 and fix it if it is affected.

What it is: CVE-2020-8116 is a high-severity vulnerability in dot-prop, published on 4 Feb 2020. 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-8116 in the wild and no public exploit code.

Affected packages and fixed versions:
- dot-prop (npm): affected all versions; fixed in 4.2.1
- dot-prop (npm): affected all versions; fixed in 4.2.1
- dot-prop (npm): affected from 5.0.0; fixed in 5.1.1
- dot-prop (npm): affected from 5.0.0; fixed in 5.1.1

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

## Sources

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

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