# GHSA-5w9c-rv96-fr7g: Removal of functional code in faker.js

> Maintainer intentionally removed functional code from faker.js, causing denial of service for applications relying on it for test data generation.

- **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:** 22 Mar 2022

## What is GHSA-5w9c-rv96-fr7g?

GHSA-5w9c-rv96-fr7g is a vulnerability in faker, published on 22 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Faker.js helps users create large amounts of data for testing and development. The maintainer deliberately removed the functional code from this package. This appears to be a purposeful and successful attempt to make the package unusable. This is related to the colors.js [CVE-2021-23567](https://github.com/advisories/GHSA-gh88-3pxp-6fm8). 

The functional code for this package was forked and can be found [here](https://github.com/faker-js/faker).

## Which versions are affected by GHSA-5w9c-rv96-fr7g?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `faker` | npm | All versions | None |
| `faker` | npm | All versions | None |

## How do I fix GHSA-5w9c-rv96-fr7g?

No fix has been published for GHSA-5w9c-rv96-fr7g yet. Limit exposure of the affected software until one is available.

## Is GHSA-5w9c-rv96-fr7g being exploited?

There is no known exploitation of GHSA-5w9c-rv96-fr7g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5w9c-rv96-fr7g and fix it if it is affected.

What it is: GHSA-5w9c-rv96-fr7g is a vulnerability in faker, published on 22 Mar 2022. 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-5w9c-rv96-fr7g in the wild and no public exploit code.

Affected packages and fixed versions:
- faker (npm): affected all versions; no fix listed
- faker (npm): affected all versions; 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-5w9c-rv96-fr7g/ (Markdown: https://insights.sbomify.com/GHSA-5w9c-rv96-fr7g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5w9c-rv96-fr7g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5w9c-rv96-fr7g/
Summaries are generated and may contain mistakes; the official description above is the record.