|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in Magento up to 188.8.131.52/184.108.40.206/2.2.11/2.3.4. It has been classified as critical. This affects an unknown functionality. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-94. 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), 220.127.116.11 and earlier, and 18.104.22.168 and earlier have a security mitigation bypass vulnerability. Successful exploitation could lead to arbitrary code execution.
The weakness was shared 06/26/2020 as APSB20-22 as confirmed security bulletin (Website). The advisory is shared at helpx.adobe.com. This vulnerability is uniquely identified as CVE-2020-9632 since 03/02/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/27/2020).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 8.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Privilege escalation
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔒
Timeline03/02/2020 CVE assigned
06/26/2020 +116 days Advisory disclosed
06/27/2020 +1 days VulDB entry created
10/27/2020 +122 days VulDB last update
CVE: CVE-2020-9632 (🔒)
See also: 🔒
EntryCreated: 06/27/2020 08:39 AM
Updated: 10/27/2020 08:04 PM
Changes: (1) advisory_confirm_url
Do you want to use VulDB in your project?
Use the official API to access entries easily!