# CVE-2021-42581: Other in n/a

> Prototype poisoning in Ramda allows attackers to compromise application integrity or availability by supplying crafted objects with __proto__ properties.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** No
- **Published:** 10 May 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x9wq-pxpv-8p4v

## What is CVE-2021-42581?

CVE-2021-42581 is a critical vulnerability in n/a, published on 10 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prototype poisoning in function mapObjIndexed in Ramda 0.27.0 and earlier allows attackers to compromise integrity or availability of application via supplying a crafted object (that contains an own property "__proto__") as an argument to the function. NOTE: the vendor disputes this because the observed behavior only means that a user can create objects that the user didn't know would contain custom prototypes

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

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

It affects 1 product.


Products: Ramdajs Ramda.

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

No fix has been published for CVE-2021-42581 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-42581 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42581 is a critical vulnerability in n/a, published on 10 May 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-42581 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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