CVE-2019-3795

published 9 Apr 2019 · updated 17 Sep 2024

Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security

3.8LowCVSS 3.8EPSS 2%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 2%. Fixed in 4.2.11.RELEASE, 5.0.11.RELEASE and 5.1.4.RELEASE.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Spring>=4.2 <4.2.11.RELEASE, >=5.0 <5.0.11.RELEASE, >=5.1 <5.1.4.RELEASE4.2.11.RELEASE, 5.0.11.RELEASE, 5.1.4.RELEASE

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2019-3795 severity on Zeptric[![CVE-2019-3795](https://zeptric.io/badge/cve/CVE-2019-3795.svg)](https://zeptric.io/cve/CVE-2019-3795)