Magento up to 1.9.4.2/1.14.4.2/2.2.9/2.3.2 Import Archive File unrestricted upload
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Magento up to 1.9.4.2/1.14.4.2/2.2.9/2.3.2. Affected by this vulnerability is an unknown functionality of the component Import Handler. The manipulation as part of Archive File leads to unrestricted upload. This vulnerability is listed as CVE-2019-8114. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Magento up to 1.9.4.2/1.14.4.2/2.2.9/2.3.2 and classified as critical. This issue affects an unknown functionality of the component Import Handler. The manipulation as part of a Archive File leads to a unrestricted upload vulnerability. Using CWE to declare the problem leads to CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A remote code execution vulnerability exists in Magento 1 prior to 1.9.4.3 and 1.14.4.3, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user with admin privileges to import features can execute arbitrary code via crafted configuration archive file upload.
The weakness was presented 11/05/2019. The identification of this vulnerability is CVE-2019-8114 since 02/12/2019. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1608.002 for this issue.
Upgrading to version 1.9.4.3, 1.14.4.3, 2.2.10, 2.3.2-p1 or 2.3.3 eliminates this vulnerability.
See VDB-145017, VDB-145016, VDB-145015 and VDB-145014 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 1.9.4.0
- 1.9.4.1
- 1.9.4.2
- 1.14.4.0
- 1.14.4.1
- 1.14.4.2
- 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.3.0
- 2.3.1
- 2.3.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Unrestricted uploadCWE: CWE-434 / CWE-284 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Magento 1.9.4.3/1.14.4.3/2.2.10/2.3.2-p1/2.3.3
Timeline
02/12/2019 🔍11/05/2019 🔍
11/06/2019 🔍
02/04/2024 🔍
Sources
Advisory: magento.comStatus: Not defined
CVE: CVE-2019-8114 (🔍)
GCVE (CVE): GCVE-0-2019-8114
GCVE (VulDB): GCVE-100-145013
See also: 🔍
Entry
Created: 11/06/2019 09:14Updated: 02/04/2024 12:37
Changes: 11/06/2019 09:14 (38), 11/06/2019 09:19 (17), 02/04/2024 12:37 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.