Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Spring | Spring Security | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1794-1 | libspring-security-2.0-java security update |
EUVD |
EUVD-2019-0437 | 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. |
Github GHSA |
GHSA-v2r2-7qm7-jj6v | Spring Security uses insufficiently random values |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 1.9% (1.921% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.