GSD-2022-1000008 faker.js 6.6.6 is broken and the developer has wiped the original GitHub repo
Not scored
Published
Check this codebase for GSD-2022-1000008 and fix it if it is affected.
What it is: GSD-2022-1000008 is a vulnerability in faker.js, published on 9 Jan 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 GSD-2022-1000008 in the wild and no public exploit code.
Affected packages and fixed versions:
- faker.js (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/GSD-2022-1000008/ (Markdown: https://insights.sbomify.com/GSD-2022-1000008/index.md)
The faker.js library was intentionally sabotaged by its maintainer, breaking dependent applications and requiring users to switch to a community fork.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is GSD-2022-1000008?
GSD-2022-1000008 is a vulnerability in faker.js, published on 9 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
faker.js had it's version updated to 6.6.6 in NPM (which reports it as having 2,571 dependent packages that rely upon it) and the GitHub repo has been wiped of content. This appears to have been done intentionally as the repo only has a single commit (so it was likjely deleted, recreated and a single commit with "endgame" added). It appears that both GitHub and NPM have locked out the original developer accountbut that the faker.js package is still broken. Please note that this issue is directly related to GSD-2022-1000007 and appears to be part of the same incident. A fork of the repo with the original code appears to now be available at https://github.com/faker-js/faker
Which versions are affected by GSD-2022-1000008?
1 open source package ship an affected version, including faker.js.
| Package | Affected | Fixed in |
|---|---|---|
faker.js npm | All versions | None |
How do I fix GSD-2022-1000008?
No fix has been published for GSD-2022-1000008 yet. Limit exposure of the affected software until one is available.
Is GSD-2022-1000008 being exploited?
There is no known exploitation of GSD-2022-1000008 in the wild and no public exploit code.