# CVE-2019-16303: JHipster Kotlin using insecure source of randomness `RandomStringUtils` before v1.2.0

> Insecure randomness in generated password reset tokens allows attackers to predict other users' reset URLs, leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 13 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j3rh-8vwq-wh84, GHSA-mwp6-j9wf-968c

## What is CVE-2019-16303?

CVE-2019-16303 is a critical vulnerability in n/a, published on 13 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A class generated by the Generator in JHipster before 6.3.0 and JHipster Kotlin through 1.1.0 produces code that uses an insecure source of randomness (apache.commons.lang3 RandomStringUtils). This allows an attacker (if able to obtain their own password reset URL) to compute the value for all other password resets for other accounts, thus allowing privilege escalation or account takeover.

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

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

4 open source packages ship an affected version, including generator-jhipster and generator-jhipster-kotlin. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `generator-jhipster` | npm | All versions | 6.3.0 |
| `generator-jhipster` | npm | All versions | 6.3.0 |
| `generator-jhipster-kotlin` | npm | All versions | 1.2.0 |
| `generator-jhipster-kotlin` | npm | All versions | 1.2.0 |

Products: Jhipster Jhipster, Jhipster Jhipster Kotlin.

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

Upgrade generator-jhipster to 6.3.0 or later.

## Is CVE-2019-16303 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-20110](https://insights.sbomify.com/CVE-2015-20110/): generator-jhipster allows a timing attack against validateToken due to a string comparison that stops at the first character (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16303 is a critical vulnerability in n/a, published on 13 Sep 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 CVE-2019-16303 in the wild and no public exploit code.

Affected packages and fixed versions:
- generator-jhipster (npm): affected all versions; fixed in 6.3.0
- generator-jhipster (npm): affected all versions; fixed in 6.3.0
- generator-jhipster-kotlin (npm): affected all versions; fixed in 1.2.0
- generator-jhipster-kotlin (npm): affected all versions; fixed in 1.2.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-16303/ (Markdown: https://insights.sbomify.com/CVE-2019-16303/index.md)
```

## Sources

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

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