# CVE-2017-18021: Weak cryptography in n/a

> QtPass generates predictable passwords, allowing attackers to enumerate and recover user credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-18021, GHSA-vxr9-mr85-jwjw, UBUNTU-CVE-2017-18021

## What is CVE-2017-18021?

CVE-2017-18021 is a critical vulnerability in n/a, published on 5 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered that QtPass before 1.2.1, when using the built-in password generator, generates possibly predictable and enumerable passwords. This only applies to the QtPass GUI.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2017-18021?

It affects 1 product.


Products: Qtpass Qtpass.

## How do I fix CVE-2017-18021?

Upgrade to a fixed version.

## Is CVE-2017-18021 being exploited?

There is no known exploitation of CVE-2017-18021 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18021 and fix it if it is affected.

What it is: CVE-2017-18021 is a critical vulnerability in n/a, published on 5 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18021 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2017-18021/ (Markdown: https://insights.sbomify.com/CVE-2017-18021/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18021
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18021
- OSV: https://osv.dev/vulnerability/CVE-2017-18021

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18021/
Summaries are generated and may contain mistakes; the official description above is the record.