CVE-2019-3795GHSA-V2R2-7QM7-JJ6V
Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.0.11.RELEASE, 5.1.4.RELEASE, 4.2.11.RELEASE, 4.2.12, 5.0.12, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Spring Spring Security
From 5.0 · fixed in 5.0.11.RELEASE; From 5.1 · fixed in 5.1.4.RELEASE; From 4.2 · fixed in 4.2.11.RELEASE
- org.springframework.security:spring-security-coreMaven
From 4.2.0 · fixed in 4.2.12
- org.springframework.security:spring-security-coreMaven
From 5.0.0 · fixed in 5.0.12
- org.springframework.security:spring-security-coreMaven
From 5.1.0 · fixed in 5.1.5