# GHSA-g9cg-h3jm-cwrc: Prototype Pollution in @hapi/subtext


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

## What is GHSA-g9cg-h3jm-cwrc?

GHSA-g9cg-h3jm-cwrc is a vulnerability in @hapi/pez, published on 3 Sep 2020. 

### Official description

Versions of `@hapi/pez` prior to 4.1.2 or 5.0.1 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

Upgrade to versions 5.0.1 or later. There is a fix available for version 4.1.2,  but it only available for direct download from the repository.

## Which versions are affected by GHSA-g9cg-h3jm-cwrc?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@hapi/pez` | npm | All versions | 5.0.1 |
| `@hapi/pez` | npm | All versions | 5.0.1 |

## How do I fix GHSA-g9cg-h3jm-cwrc?

Upgrade @hapi/pez to 5.0.1 or later.

## Is GHSA-g9cg-h3jm-cwrc being exploited?

There is no known exploitation of GHSA-g9cg-h3jm-cwrc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g9cg-h3jm-cwrc and fix it if it is affected.

What it is: GHSA-g9cg-h3jm-cwrc is a vulnerability in @hapi/pez, published on 3 Sep 2020. 
Exploitation: There is no known exploitation of GHSA-g9cg-h3jm-cwrc in the wild and no public exploit code.

Affected packages and fixed versions:
- @hapi/pez (npm): affected all versions; fixed in 5.0.1
- @hapi/pez (npm): affected all versions; fixed in 5.0.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/GHSA-g9cg-h3jm-cwrc/ (Markdown: https://insights.sbomify.com/GHSA-g9cg-h3jm-cwrc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g9cg-h3jm-cwrc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g9cg-h3jm-cwrc/
Summaries are generated and may contain mistakes; the official description above is the record.