# CVE-2019-10792: Injection in bodymen

> Prototype pollution in bodymen allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8h84-8j4f-p97q, SNYK-JS-BODYMEN-548897

## What is CVE-2019-10792?

CVE-2019-10792 is a medium-severity vulnerability in Snyk bodymen, published on 18 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2019-10792?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bodymen` | npm | All versions | 1.1.1 |
| `bodymen` | npm | All versions | 1.1.1 |

Products: Bodymen Project Bodymen.

## How do I fix CVE-2019-10792?

Upgrade bodymen to 1.1.1 or later.

## Is CVE-2019-10792 being exploited?

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

## Other vulnerabilities in Snyk bodymen

- [CVE-2022-25296](https://insights.sbomify.com/CVE-2022-25296/): Prototype Pollution (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10792 and fix it if it is affected.

What it is: CVE-2019-10792 is a medium-severity vulnerability in Snyk bodymen, published on 18 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10792 in the wild and no public exploit code.

Affected packages and fixed versions:
- bodymen (npm): affected all versions; fixed in 1.1.1
- bodymen (npm): affected all versions; fixed in 1.1.1

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

## Sources

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

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