WSO2 Identity Server/IS as Key Manager up to 5.9.0 Management Console Policy Administration Reflected cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in WSO2 Identity Server and IS as Key Manager up to 5.9.0. Affected by this issue is some unknown functionality of the component Management Console Policy Administration. This manipulation causes cross site scripting (Reflected). The identification of this vulnerability is CVE-2020-14444. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in WSO2 Identity Server and IS as Key Manager up to 5.9.0. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Management Console Policy Administration. The manipulation with an unknown input leads to a cross site scripting vulnerability (Reflected). The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect integrity. The summary by CVE is:
An issue was discovered in WSO2 Identity Server through 5.9.0 and WSO2 IS as Key Manager through 5.9.0. A potential Reflected Cross-Site Scripting (XSS) vulnerability has been identified in the Management Console Policy Administration user interface.
The weakness was shared 06/18/2020 (Website). The advisory is shared at docs.wso2.com. This vulnerability is known as CVE-2020-14444 since 06/18/2020. The attack can be launched remotely. A single authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-156951 and VDB-156950 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.1
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: 🔍
Exploiting
Name: ReflectedClass: Cross site scripting / Reflected
CWE: CWE-80 / 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
06/18/2020 🔍06/18/2020 🔍
06/19/2020 🔍
10/25/2020 🔍
Sources
Advisory: docs.wso2.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-14444 (🔍)
GCVE (CVE): GCVE-0-2020-14444
GCVE (VulDB): GCVE-100-156949
See also: 🔍
Entry
Created: 06/19/2020 07:02Updated: 10/25/2020 13:32
Changes: 06/19/2020 07:02 (39), 06/19/2020 07:07 (11), 10/25/2020 13:23 (1), 10/25/2020 13:32 (1)
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.