| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Magento up to 1.9.4.3/1.14.4.3/2.2.10/2.3.3. Affected by this vulnerability is an unknown functionality. This manipulation causes sql injection. This vulnerability is registered as CVE-2020-3719. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical was found in Magento up to 1.9.4.3/1.14.4.3/2.2.10/2.3.3. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Magento versions 2.3.3 and earlier, 2.2.10 and earlier, 1.14.4.3 and earlier, and 1.9.4.3 and earlier have an sql injection vulnerability. Successful exploitation could lead to sensitive information disclosure.
The weakness was published 01/29/2020 as APSB20-02 as confirmed security bulletin (Website). The advisory is shared at helpx.adobe.com. This vulnerability is known as CVE-2020-3719 since 12/17/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
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-149541, VDB-149542, VDB-149543 and VDB-149544. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 1.9.4.0
- 1.9.4.1
- 1.9.4.2
- 1.9.4.3
- 1.14.4.0
- 1.14.4.1
- 1.14.4.2
- 1.14.4.3
- 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.3.0
- 2.3.1
- 2.3.2
- 2.3.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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
12/17/2019 🔍01/29/2020 🔍
01/30/2020 🔍
01/30/2020 🔍
Sources
Advisory: APSB20-02Status: Confirmed
CVE: CVE-2020-3719 (🔍)
GCVE (CVE): GCVE-0-2020-3719
GCVE (VulDB): GCVE-100-149545
See also: 🔍
Entry
Created: 01/30/2020 08:33Updated: 01/30/2020 08:38
Changes: 01/30/2020 08:33 (38), 01/30/2020 08:38 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.