# GHSA-qccf-q7p4-3q3j: Prototype Pollution in safe-object2

> Prototype pollution in safe-object2 allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2020

## What is GHSA-qccf-q7p4-3q3j?

GHSA-qccf-q7p4-3q3j is a vulnerability in safe-object2, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `safe-object2` are vulnerable to prototype pollution. The `settter()` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.

## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-qccf-q7p4-3q3j?

2 open source packages ship an affected version, including safe-object2.


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

## How do I fix GHSA-qccf-q7p4-3q3j?

No fix has been published for GHSA-qccf-q7p4-3q3j yet. Limit exposure of the affected software until one is available.

## Is GHSA-qccf-q7p4-3q3j being exploited?

There is no known exploitation of GHSA-qccf-q7p4-3q3j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qccf-q7p4-3q3j and fix it if it is affected.

What it is: GHSA-qccf-q7p4-3q3j is a vulnerability in safe-object2, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-qccf-q7p4-3q3j in the wild and no public exploit code.

Affected packages and fixed versions:
- safe-object2 (npm): affected from 0.0.0; no fix listed
- safe-object2 (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/GHSA-qccf-q7p4-3q3j/ (Markdown: https://insights.sbomify.com/GHSA-qccf-q7p4-3q3j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qccf-q7p4-3q3j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qccf-q7p4-3q3j/
Summaries are generated and may contain mistakes; the official description above is the record.