# CVE-2019-10754: Use of Insufficiently Random Values in Apereo CAS

> Predictable token generation in Apereo CAS allows attackers to bypass authentication or take over accounts due to weak random number generation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g24w-373r-5pxg

## What is CVE-2019-10754?

CVE-2019-10754 is a high-severity vulnerability in Apereo CAS, published on 23 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple classes used within Apereo CAS before release 6.1.0-RC5 makes use of apache commons-lang3 RandomStringUtils for token and ID generation which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong.

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

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

12 open source packages ship an affected version, including org.apereo.cas:cas-server-core-services-api, org.apereo.cas:cas-server-core-services-authentication and org.apereo.cas:cas-server-support-oauth-core-api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apereo.cas:cas-server-core-services-api` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-core-services-api` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-core-services-authentication` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-core-services-authentication` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-oauth-core-api` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-oauth-core-api` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-oidc` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-oidc` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-shell` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-shell` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-simple-mfa` | Maven | All versions | 6.1.0-RC5 |
| `org.apereo.cas:cas-server-support-simple-mfa` | Maven | All versions | 6.1.0-RC5 |

Products: Apereo Central Authentication Service.

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

Upgrade org.apereo.cas:cas-server-core-services-api to 6.1.0-RC5 or later.

## Is CVE-2019-10754 being exploited?

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

## Other vulnerabilities in Apereo CAS

- [CVE-2023-4612](https://insights.sbomify.com/CVE-2023-4612/): MFA bypass in Apereo CAS (critical 9.8)
- [CVE-2024-4399](https://insights.sbomify.com/CVE-2024-4399/): CAS <= 1.0.0 - Unauthenticated SSRF (critical 9.1)
- [CVE-2020-27178](https://insights.sbomify.com/CVE-2020-27178/): Improper Authentication in Apereo CAS (high 7.5)
- [CVE-2015-1169](https://insights.sbomify.com/CVE-2015-1169/): Auth bypass in n/a (high 7.5)
- [CVE-2024-11208](https://insights.sbomify.com/CVE-2024-11208/): Apereo CAS login session expiration (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10754 is a high-severity vulnerability in Apereo CAS, published on 23 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10754 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apereo.cas:cas-server-core-services-api (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-core-services-api (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-core-services-authentication (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-core-services-authentication (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-oauth-core-api (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-oauth-core-api (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-oidc (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-oidc (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-shell (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-shell (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-simple-mfa (Maven): affected all versions; fixed in 6.1.0-RC5
- org.apereo.cas:cas-server-support-simple-mfa (Maven): affected all versions; fixed in 6.1.0-RC5

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

## Sources

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

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