Spring Security up to 4.2.11/5.0.11/5.1.4 random entropy

Summaryinfo

A vulnerability was found in Spring Security up to 4.2.11/5.0.11/5.1.4. It has been rated as problematic. Impacted is an unknown function. The manipulation leads to entropy (random). This vulnerability is traded as CVE-2019-3795. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Spring Security up to 4.2.11/5.0.11/5.1.4 and classified as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a entropy vulnerability (Random). Using CWE to declare the problem leads to CWE-332. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. Impacted is confidentiality. The summary by CVE is:

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.

The bug was discovered 04/02/2019. The weakness was shared 04/09/2019 (Website). It is possible to read the advisory at pivotal.io. The identification of this vulnerability is CVE-2019-3795 since 01/03/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176937 (Debian Security Update for libspring-security-2.0-java (DLA 1794-1)).

Upgrading to version 4.2.12, 5.0.12 or 5.1.5 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Spring Security

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6
• 5.0.7
• 5.0.8
• 5.0.9
• 5.0.10
• 5.0.11
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion