# CVE-2020-28495: Prototype Pollution

> Prototype pollution in total.js allows attackers to cause denial of service or remote code execution via unsanitized path keys.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6cf8-qhqj-vjqm, SNYK-JS-TOTALJS-1046671

## What is CVE-2020-28495?

CVE-2020-28495 is a high-severity vulnerability in total.js, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects the package total.js before 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the application. In some cases it is possible to achieve Denial of service (DoS), Remote Code Execution or Property Injection.

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

2 open source packages ship an affected version, including total.js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `total.js` | npm | All versions | 3.4.7 |
| `total.js` | npm | All versions | 3.4.7 |

Products: Totaljs Total.js.

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

Upgrade total.js to 3.4.7 or later.

## Is CVE-2020-28495 being exploited?

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

## Other vulnerabilities in total.js

- [CVE-2021-23389](https://insights.sbomify.com/CVE-2021-23389/): Arbitrary Code Execution (critical 9.8)
- [CVE-2021-23344](https://insights.sbomify.com/CVE-2021-23344/): Remote Code Execution (RCE) (critical 9.8)
- [CVE-2024-48655](https://insights.sbomify.com/CVE-2024-48655/): Code injection in n/a (high 8.8)
- [CVE-2022-44019](https://insights.sbomify.com/CVE-2022-44019/): Command injection in n/a (high 8.8)
- [CVE-2020-28494](https://insights.sbomify.com/CVE-2020-28494/): Command Injection (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28495 is a high-severity vulnerability in total.js, published on 2 Feb 2021. 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-28495 in the wild and no public exploit code.

Affected packages and fixed versions:
- total.js (npm): affected all versions; fixed in 3.4.7
- total.js (npm): affected all versions; fixed in 3.4.7

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

## Sources

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

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