# CVE-2019-10682: django-nopassword stores secrets in cleartext

> An attacker with database access can read cleartext secrets stored by the django-nopassword library, compromising user credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-37cf-r3w2-gjfw, PYSEC-2020-229

## What is CVE-2019-10682?

CVE-2019-10682 is a high-severity vulnerability in n/a, published on 18 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

django-nopassword before 5.0.0 stores cleartext secrets in the database.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2019-10682?

3 open source packages ship an affected version, including django-nopassword. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django-nopassword` | PyPI | All versions | 5.0.0 |
| `django-nopassword` | PyPI | All versions | 5.0.0 |
| `django-nopassword` | PyPI | All versions | 5.0.0 |

Products: Django-Nopassword Project Django-Nopassword.

## How do I fix CVE-2019-10682?

Upgrade django-nopassword to 5.0.0 or later.

## Is CVE-2019-10682 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10682 and fix it if it is affected.

What it is: CVE-2019-10682 is a high-severity vulnerability in n/a, published on 18 Mar 2020. 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-2019-10682 in the wild and no public exploit code.

Affected packages and fixed versions:
- django-nopassword (PyPI): affected all versions; fixed in 5.0.0
- django-nopassword (PyPI): affected all versions; fixed in 5.0.0
- django-nopassword (PyPI): affected all versions; fixed in 5.0.0

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

## Sources

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

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