# CVE-2022-25296: Prototype Pollution

> Attackers can pollute Object.prototype via the handler function, potentially leading to code execution or security bypasses in applications using the bodymen library.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vhxc-fhm5-qcp9

## What is CVE-2022-25296?

CVE-2022-25296 is a medium-severity vulnerability in bodymen, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The package bodymen from 0.0.0 are vulnerable to Prototype Pollution via the handler function which could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload. **Note:** This vulnerability derives from an incomplete fix to [CVE-2019-10792](https://security.snyk.io/vuln/SNYK-JS-BODYMEN-548897)

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

## Which versions are affected by CVE-2022-25296?

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


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

Products: Bodymen Project Bodymen.

## How do I fix CVE-2022-25296?

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

## Is CVE-2022-25296 being exploited?

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

## Other vulnerabilities in bodymen

- [CVE-2019-10792](https://insights.sbomify.com/CVE-2019-10792/): Injection in bodymen (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25296 and fix it if it is affected.

What it is: CVE-2022-25296 is a medium-severity vulnerability in bodymen, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25296 in the wild and no public exploit code.

Affected packages and fixed versions:
- bodymen (npm): affected from 0.0.0; no fix listed
- bodymen (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-2022-25296/ (Markdown: https://insights.sbomify.com/CVE-2022-25296/index.md)
```

## Sources

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

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