# CVE-2022-25862: Prototype Pollution

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

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-ph28-wwfj-fv7f

## What is CVE-2022-25862?

CVE-2022-25862 is a medium-severity vulnerability in sds, published on 13 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This affects the package sds from 0.0.0. The library could be tricked into adding or modifying properties of the Object.prototype by abusing the set function located in js/set.js. **Note:** This vulnerability derives from an incomplete fix to [CVE-2020-7618](https://security.snyk.io/vuln/SNYK-JS-SDS-564123)

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sds` | npm | All versions to 4.4.0 | None |
| `sds` | npm | All versions to 4.4.0 | None |

Products: Sds Project Sds.

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

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

## Is CVE-2022-25862 being exploited?

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

## Other vulnerabilities in sds

- [CVE-2020-7618](https://insights.sbomify.com/CVE-2020-7618/): Prototype Pollution in sds (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25862 is a medium-severity vulnerability in sds, published on 13 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25862 in the wild and no public exploit code.

Affected packages and fixed versions:
- sds (npm): affected all versions up to 4.4.0; no fix listed
- sds (npm): affected all versions up to 4.4.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-25862/ (Markdown: https://insights.sbomify.com/CVE-2022-25862/index.md)
```

## Sources

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

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