Spring Security up to 5.2.3/5.3.1 Signature SAML Response signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Spring Security up to 5.2.3/5.3.1. The impacted element is an unknown function of the component Signature Handler. Such manipulation as part of SAML Response leads to signature verification. This vulnerability is listed as CVE-2020-5407. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in Spring Security up to 5.2.3/5.3.1 and classified as critical. Affected by this issue is an unknown part of the component Signature Handler. The manipulation as part of a SAML Response leads to a signature verification vulnerability. Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully modify an otherwise valid SAML response and append an arbitrary assertion that Spring Security will accept as valid.
The weakness was presented 05/13/2020 (Website). The advisory is shared for download at tanzu.vmware.com. This vulnerability is handled as CVE-2020-5407 since 01/03/2020. The exploitation is known to be easy. The attack may be launched remotely. A simple authentication is necessary for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 5.2.4 or 5.3.2 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Spring Security 5.2.4/5.3.2
Timeline
01/03/2020 🔍05/13/2020 🔍
05/14/2020 🔍
10/18/2020 🔍
Sources
Advisory: tanzu.vmware.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-5407 (🔍)
GCVE (CVE): GCVE-0-2020-5407
GCVE (VulDB): GCVE-100-155228
Entry
Created: 05/14/2020 09:13Updated: 10/18/2020 07:13
Changes: 05/14/2020 09:13 (39), 05/14/2020 09:18 (17), 10/18/2020 07:13 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.