# CVE-2020-8147: Prototype Pollution

> Prototype pollution in utils-extend allows attackers to achieve remote code execution or denial of service in applications using the library.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6pq3-928q-x6w6

## What is CVE-2020-8147?

CVE-2020-8147 is a critical code injection vulnerability in utils-extend, published on 3 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Flaw in input validation in npm package utils-extend version 1.0.8 and earlier may allow prototype pollution attack that may result in remote code execution or denial of service of applications using utils-extend.

Weakness: CWE-20 (Improper Input Validation), CWE-471 (Modification of Assumed-Immutable Data (MAID))

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

2 open source packages ship an affected version, including utils-extend. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `utils-extend` | npm | From 0.0.0 | None |
| `utils-extend` | npm | From 0.0.0 | None |

Products: Utils-Extend Project Utils-Extend.

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

Upgrade to a fixed version.

## Is CVE-2020-8147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8147 is a critical code injection vulnerability in utils-extend, published on 3 Apr 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-8147 in the wild and no public exploit code.

Affected packages and fixed versions:
- utils-extend (npm): affected from 0.0.0; no fix listed
- utils-extend (npm): affected from 0.0.0; no fix listed

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

## Sources

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

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