Spring Security up to 4.2.15/5.0.15/5.1.9/5.2.3/5.3.1 CBC Mode predictable iv with cbc

Summaryinfo

A vulnerability was found in Spring Security up to 4.2.15/5.0.15/5.1.9/5.2.3/5.3.1. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component CBC Mode Handler. The manipulation leads to predictable iv with cbc. This vulnerability is traded as CVE-2020-5408. 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.15/5.0.15/5.1.9/5.2.3/5.3.1 and classified as problematic. This issue affects an unknown function of the component CBC Mode Handler. The manipulation with an unknown input leads to a predictable iv with cbc vulnerability. Using CWE to declare the problem leads to CWE-329. The product generates and uses a predictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode, which causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key. Impacted is confidentiality. The summary by CVE is:

Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text encryptor. A malicious user with access to the data that has been encrypted using such an encryptor may be able to derive the unencrypted values using a dictionary attack.

The weakness was shared 05/14/2020 (Website). The advisory is shared at tanzu.vmware.com. The identification of this vulnerability is CVE-2020-5408 since 01/03/2020. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 4.2.16, 5.0.16, 5.1.10, 5.2.4 or 5.3.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 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.0.12
• 5.0.13
• 5.0.14
• 5.0.15
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5
• 5.1.6
• 5.1.7
• 5.1.8
• 5.1.9
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.3.0
• 5.3.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion