# GHSA-g64q-3vg8-8f93: Prototype Pollution in pez


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-g64q-3vg8-8f93?

GHSA-g64q-3vg8-8f93 is a vulnerability in pez, published on 3 Sep 2020. 

### Official description

All versions of `pez` are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.

## Recommendation

This package is deprecated and is now maintained as `@hapi/pez`. Please update your dependencies to use `@hapi/pez`.

## Which versions are affected by GHSA-g64q-3vg8-8f93?

2 open source packages ship an affected version, including pez.


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

## How do I fix GHSA-g64q-3vg8-8f93?

No fix has been published for GHSA-g64q-3vg8-8f93 yet. Limit exposure of the affected software until one is available.

## Is GHSA-g64q-3vg8-8f93 being exploited?

There is no known exploitation of GHSA-g64q-3vg8-8f93 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g64q-3vg8-8f93 and fix it if it is affected.

What it is: GHSA-g64q-3vg8-8f93 is a vulnerability in pez, published on 3 Sep 2020. 
Exploitation: There is no known exploitation of GHSA-g64q-3vg8-8f93 in the wild and no public exploit code.

Affected packages and fixed versions:
- pez (npm): affected from 0.0.0; no fix listed
- pez (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-g64q-3vg8-8f93/ (Markdown: https://insights.sbomify.com/GHSA-g64q-3vg8-8f93/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g64q-3vg8-8f93

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g64q-3vg8-8f93/
Summaries are generated and may contain mistakes; the official description above is the record.