Skip to content
Fencer Intel
low 3.8

CVE-2019-3795 json

Insecure Randomness When Using a SecureRandom Instance Constructed by Spring Security

published 7y ago modified 4mo ago also GHSA-v2r2-7qm7-jj6v , EUVD-2019-0437

cvss
3.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

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.

Patch / fix

  • maven org.springframework.security:spring-security-core 4.2.12, 5.0.12, 5.1.5
  • Spring Spring Security 4.2.11.RELEASE, 5.0.11.RELEASE, 5.1.4.RELEASE

Is CVE-2019-3795 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-3795 updated cvss 3.3

spring-security-core: Insecure randomness when using a secureRandom instance constructed by Spring Security

  • Red Hat Fuse 7 spring-security-core
    affected: no fix available “Fix deferred”
  • Red Hat JBoss Fuse 6 spring-security-core
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 9 (Mitaka) opendaylight Red Hat OpenStack Platform 10 (Newton) opendaylight
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 8 (Liberty) opendaylight Red Hat OpenStack Platform 13 (Queens) opendaylight Red Hat OpenStack Platform 14 (Rocky) opendaylight
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.92% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 3.8 CVSS:3.0/AV:P/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-core
>=4.2.0, <4.2.12
>=5.0.0, <5.0.12
>=5.1.0, <5.1.5
4.2.12
5.0.12
5.1.5

Affected products

  • Spring Spring Security

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.