CVE-2019-3795

Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security

Description

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.

Category

5.3
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 3.0 •
CVSS 2.0 •
EPSS 1.96% Top 20%
Vendor Advisory pivotal.io
Affected: Spring Spring Security
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2019-3795?
CVE-2019-3795 has been scored as a medium severity vulnerability.
How to fix CVE-2019-3795?
To fix CVE-2019-3795, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-3795 being actively exploited in the wild?
It is possible that CVE-2019-3795 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2019-3795?
CVE-2019-3795 affects Spring Spring Security.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.