Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security
Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-core Maven |
|
|
Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-core Maven |
|
|
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.
From the CVE record · dell
Spring Security uses insecure randomness when an application configures a SecureRandom instance with SecureRandomFactoryBean#setSeed. An attacker could exploit this only if the application supplies a seed and makes the resulting random material available for inspection. The input does not specify whether network access, authentication, or user interaction is required.
Teams using Maven org.springframework.security:spring-security-core versions 4.2.0–4.2.11, 5.0.0–5.0.11, or 5.1.0–5.1.4 should check their use of SecureRandomFactoryBean#setSeed.