Magento up to 1.9.4.4/1.14.4.4/2.2.11/2.3.4 Signature Validation information exposure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Magento up to 1.9.4.4/1.14.4.4/2.2.11/2.3.4. Impacted is an unknown function of the component Signature Validation. Performing a manipulation results in information exposure. This vulnerability is identified as CVE-2020-9588. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Magento up to 1.9.4.4/1.14.4.4/2.2.11/2.3.4. It has been classified as problematic. This affects an unknown code of the component Signature Validation. The manipulation with an unknown input leads to a information exposure vulnerability. CWE is classifying the issue as CWE-203. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have an observable timing discrepancy vulnerability. Successful exploitation could lead to signature verification bypass.
The weakness was released 06/26/2020 as APSB20-22 as confirmed security bulletin (Website). It is possible to read the advisory at helpx.adobe.com. This vulnerability is uniquely identified as CVE-2020-9588 since 03/02/2020. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-157359, VDB-157360, VDB-157361 and VDB-157362. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 1.9.4.0
- 1.9.4.1
- 1.9.4.2
- 1.9.4.3
- 1.9.4.4
- 1.14.4.0
- 1.14.4.1
- 1.14.4.2
- 1.14.4.3
- 1.14.4.4
- 2.2.0
- 2.2.1
- 2.2.2
- 2.2.3
- 2.2.4
- 2.2.5
- 2.2.6
- 2.2.7
- 2.2.8
- 2.2.9
- 2.2.10
- 2.2.11
- 2.3.0
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: Information exposureCWE: CWE-203 / CWE-200 / CWE-284
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/02/2020 🔍06/26/2020 🔍
06/27/2020 🔍
10/27/2020 🔍
Sources
Advisory: APSB20-22Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-9588 (🔍)
GCVE (CVE): GCVE-0-2020-9588
GCVE (VulDB): GCVE-100-157371
See also: 🔍
Entry
Created: 06/27/2020 08:36Updated: 10/27/2020 18:28
Changes: 06/27/2020 08:36 (40), 06/27/2020 08:41 (17), 10/27/2020 18:28 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.