Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security
Spring Security versions 4.2.x prior to 4.2.12, 5.0.x prior to 5.0.12, and 5.1.x prior to 5.1.5 contain an insecure randomness vulnerability when using SecureRandomFactoryBean#setSeed to configure a SecureRandom instance. In order to be impacted, an honest application must provide a seed and make the resulting random material available to an attacker for inspection.
- Published
- Apr 9, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-330
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
CNA vs NVD score
- NVD
- 5.3
- CNA · dell
- 3.8
- 1.5 point gap
CVSS:3.0/AV:P/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring security | cpe:2.3:a:vmware:spring_security |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- vmware spring security4.2.0 and later · before 4.2.12
- vmware spring security5.0.0 and later · before 5.0.12
- vmware spring security5.1.0 and later · before 5.1.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.
Spring Spring Security
- 5.0 and later · before 5.0.11.RELEASEaffected
- 5.1 and later · before 5.1.4.RELEASEaffected
- 4.2 and later · before 4.2.11.RELEASEaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:8 | libspring-security-2.0-java | before 2.0.7.RELEASE-3+deb8u1 | 2.0.7.RELEASE-3+deb8u1 |
| Maven | org.springframework.security:spring-security-core | from 4.2.0 · before 4.2.12 | 4.2.12 |
| Maven | org.springframework.security:spring-security-core | from 5.0.0 · before 5.0.12 | 5.0.12 |
| Maven | org.springframework.security:spring-security-core | from 5.1.0 · before 5.1.5 | 5.1.5 |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22978In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigure43Plan
- CVE-2023-34034Using "**" as a pattern in Spring Security configuration
for WebFlux creates a mismatch in pattern matching between Spring
Security and Sp40Plan
- CVE-2022-31692Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or includ40Plan
- CVE-2014-3527When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service int40Plan
- CVE-2026-59270Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces36Monitor
- CVE-2026-22732Under Some Conditions Spring Security HTTP Headers Are not Written36Monitor
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 |
|---|---|---|
| debian:libspring-security-2.0-java | 2.0.7.RELEASE-3+deb8u1 · Debian:8 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 4.2.12 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 5.0.12 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 5.1.5 | 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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-330 · Use of Insufficiently Random ValuesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securityfocus.com/bid/107802
- lists.debian.org/debian-lts-announce/2019/05/msg00026.html
- pivotal.io/security/cve-2019-3795
Vendor advisories and official records. Exploit/PoC links are deliberately left out.