WSO2 API Manager/API Microgateway/IS as Key Manager Management Console xml external entity reference
|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 classified as critical has been found in WSO2 API Manager, API Microgateway and IS as Key Manager (Automation Software) (the affected version unknown). This affects some unknown functionality of the component Management Console. The manipulation with an unknown input leads to a xml external entity vulnerability. CWE is classifying the issue as CWE-611. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In WSO2 API Manager 3.0.0 and earlier, WSO2 API Microgateway 2.2.0, and WSO2 IS as Key Manager 5.9.0 and earlier, Management Console allows XXE during addition or update of a Lifecycle.
The weakness was shared 06/06/2020. This vulnerability is uniquely identified as CVE-2020-13883 since 06/06/2020. It is possible to initiate the attack remotely. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available.
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: 5.1
VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
ExploitingClass: XML External Entity
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
06/06/2020 +0 days 🔍
06/07/2020 +1 days 🔍
10/22/2020 +137 days 🔍
SourcesStatus: Not defined
CVE: CVE-2020-13883 (🔍)
EntryCreated: 06/07/2020 12:13 PM
Updated: 10/22/2020 05:35 PM
Changes: (1) source_cve_cna
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!