Multiple classes used within Apereo CAS before release 6.1.0-RC5 makes use of apache commons-lang3 RandomStringUtils for token and ID genera
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.
- Published
- Sep 23, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 77th percentile
- CWE
- CWE-338
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| apereo | central authentication service | cpe:2.3:a:apereo:central_authentication_service |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apereo central authentication serviceup to 6.0.5.1 inclusive
- apereo central authentication service6.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (snyk). Independent of NVD's CPE analysis and usually ahead of it.
n/a Apereo CAS
- All versions prior to version 6.1.0-RC5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apereo.cas:cas-server-core-services-api | before 6.1.0-RC5 | 6.1.0-RC5 |
| Maven | org.apereo.cas:cas-server-core-services-authentication | before 6.1.0-RC5 | 6.1.0-RC5 |
| Maven | org.apereo.cas:cas-server-support-oauth-core-api | before 6.1.0-RC5 | 6.1.0-RC5 |
| Maven | org.apereo.cas:cas-server-support-oidc | before 6.1.0-RC5 | 6.1.0-RC5 |
| Maven | org.apereo.cas:cas-server-support-shell | before 6.1.0-RC5 | 6.1.0-RC5 |
| Maven | org.apereo.cas:cas-server-support-simple-mfa | before 6.1.0-RC5 | 6.1.0-RC5 |
Same product
apereo: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4612MFA bypass in Apereo CAS39Monitor
- CVE-2024-4399CAS <= 1.0.0 - Unauthenticated SSRF37Monitor
- CVE-2015-1169Apereo Central Authentication Service (CAS) Server before 3.5.3 allows remote attackers to conduct LDAP injection attacks via a crafted user31Monitor
- CVE-2023-28857LDAP password leak in Apereo CAS - GHSL-2023-00930Monitor
- CVE-2020-27178Apereo CAS 5.3.x before 5.3.16, 6.x before 6.1.7.2, 6.2.x before 6.2.4, and 6.3.x before 6.3.0-RC4 mishandles secret keys with Google Authen30Monitor
- CVE-2021-42567Apereo CAS through 6.4.1 allows XSS via POST requests sent to the REST API endpoints.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.apereo.cas:cas-server-core-services-api | 6.1.0-RC5 | Package registry (OSV) |
| Maven:org.apereo.cas:cas-server-core-services-authentication | 6.1.0-RC5 | Package registry (OSV) |
| Maven:org.apereo.cas:cas-server-support-oauth-core-api | 6.1.0-RC5 | Package registry (OSV) |
| Maven:org.apereo.cas:cas-server-support-oidc | 6.1.0-RC5 | Package registry (OSV) |
| Maven:org.apereo.cas:cas-server-support-shell | 6.1.0-RC5 | Package registry (OSV) |
| Maven:org.apereo.cas:cas-server-support-simple-mfa | 6.1.0-RC5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →