Magento up to 1.9.4.4/1.14.4.4/2.2.11/2.3.4 Authorization authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Magento up to 1.9.4.4/1.14.4.4/2.2.11/2.3.4. This issue affects some unknown processing of the component Authorization. Such manipulation leads to authorization. This vulnerability is referenced as CVE-2020-9587. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Magento up to 1.9.4.4/1.14.4.4/2.2.11/2.3.4 and classified as critical. Affected by this issue is an unknown part of the component Authorization. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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 authorization bypass vulnerability. Successful exploitation could lead to potentially unauthorized product discounts.
The weakness was published 06/26/2020 as APSB20-22 as confirmed security bulletin (Website). The advisory is available at helpx.adobe.com. This vulnerability is handled as CVE-2020-9587 since 03/02/2020. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-157359, VDB-157360, VDB-157361 and VDB-157362. If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
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-9587 (🔍)
GCVE (CVE): GCVE-0-2020-9587
GCVE (VulDB): GCVE-100-157370
See also: 🔍
Entry
Created: 06/27/2020 08:35Updated: 10/27/2020 18:23
Changes: 06/27/2020 08:35 (39), 06/27/2020 08:40 (17), 10/27/2020 18:23 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.