# GHSA-6qqf-vvcr-7qrv: Cryptographically Weak PRNG in generate-password

> Weak random number generation in generate-password creates biased, guessable passwords, allowing attackers to bypass authentication.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2019

## What is GHSA-6qqf-vvcr-7qrv?

GHSA-6qqf-vvcr-7qrv is a vulnerability in generate-password, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of generate-password generate random values that are biased towards certain characters depending on the chosen character sets. This may result in guessable passwords.

## Recommendation

Update to version 1.4.1 or later.

## Which versions are affected by GHSA-6qqf-vvcr-7qrv?

2 open source packages ship an affected version, including generate-password.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `generate-password` | npm | All versions | 1.4.1 |
| `generate-password` | npm | All versions | 1.4.1 |

## How do I fix GHSA-6qqf-vvcr-7qrv?

Upgrade generate-password to 1.4.1 or later.

## Is GHSA-6qqf-vvcr-7qrv being exploited?

There is no known exploitation of GHSA-6qqf-vvcr-7qrv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6qqf-vvcr-7qrv and fix it if it is affected.

What it is: GHSA-6qqf-vvcr-7qrv is a vulnerability in generate-password, published on 23 May 2019. 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-6qqf-vvcr-7qrv in the wild and no public exploit code.

Affected packages and fixed versions:
- generate-password (npm): affected all versions; fixed in 1.4.1
- generate-password (npm): affected all versions; fixed in 1.4.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-6qqf-vvcr-7qrv/ (Markdown: https://insights.sbomify.com/GHSA-6qqf-vvcr-7qrv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6qqf-vvcr-7qrv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6qqf-vvcr-7qrv/
Summaries are generated and may contain mistakes; the official description above is the record.