# CVE-2021-23507: Prototype Pollution

> Prototype pollution in object-path-set allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P`)
- **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 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h6pr-c536-6rjg, SNYK-JS-OBJECTPATHSET-2388576

## What is CVE-2021-23507?

CVE-2021-23507 is a high-severity vulnerability in object-path-set, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package object-path-set before 1.0.2 are vulnerable to Prototype Pollution via the setPath method, as it allows an attacker to merge object prototypes into it. *Note:* This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-OBJECTPATHSET-607908

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

2 open source packages ship an affected version, including object-path-set. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `object-path-set` | npm | All versions | 1.0.2 |
| `object-path-set` | npm | All versions | 1.0.2 |

Products: Skratchdot Object-Path-Set.

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

Upgrade object-path-set to 1.0.2 or later.

## Is CVE-2021-23507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-23507 is a high-severity vulnerability in object-path-set, published on 4 Feb 2022. 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-2021-23507 in the wild and no public exploit code.

Affected packages and fixed versions:
- object-path-set (npm): affected all versions; fixed in 1.0.2
- object-path-set (npm): affected all versions; fixed in 1.0.2

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

## Sources

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

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