# CVE-2021-23497: Prototype Pollution

> Prototype pollution in the @strikeentco/set library allows attackers to cause denial of service and potentially execute remote code.

- **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:** 16 Sep 2024
- **Also known as:** GHSA-39qv-prmh-x37f, SNYK-JS-STRIKEENTCOSET-2385945

## What is CVE-2021-23497?

CVE-2021-23497 is a high-severity vulnerability in @strikeentco/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

This affects the package @strikeentco/set before 1.0.2. It allows an attacker to cause a denial of service and may lead to remote code execution. **Note:** This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-STRIKEENTCOSET-1038821

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

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

2 open source packages ship an affected version, including @strikeentco/set. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@strikeentco/set` | npm | All versions | 1.0.2 |
| `@strikeentco/set` | npm | All versions | 1.0.2 |

Products: Set Project Set.

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

Upgrade @strikeentco/set to 1.0.2 or later.

## Is CVE-2021-23497 being exploited?

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

## Other vulnerabilities in @strikeentco/set

- [CVE-2020-28267](https://insights.sbomify.com/CVE-2020-28267/): Prototype pollution in @strikeentco/set (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-23497 is a high-severity vulnerability in @strikeentco/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-23497 in the wild and no public exploit code.

Affected packages and fixed versions:
- @strikeentco/set (npm): affected all versions; fixed in 1.0.2
- @strikeentco/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-23497/ (Markdown: https://insights.sbomify.com/CVE-2021-23497/index.md)
```

## Sources

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

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