SmartClient 12.0 developerConsoleOperations.jsp _transaction xml entity expansion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SmartClient 12.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /tools/developerConsoleOperations.jsp. The manipulation of the argument _transaction as part of POST Request leads to xml entity expansion. This vulnerability is uniquely identified as CVE-2020-9352. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in SmartClient 12.0. This issue affects an unknown function of the file /tools/developerConsoleOperations.jsp. The manipulation of the argument _transaction as part of a POST Request leads to a xml entity expansion vulnerability. Using CWE to declare the problem leads to CWE-776. The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in SmartClient 12.0. Unauthenticated exploitation of blind XXE can occur in the downloadWSDL feature by sending a POST request to /tools/developerConsoleOperations.jsp with a valid payload in the _transaction parameter.
The weakness was disclosed 02/23/2020. The identification of this vulnerability is CVE-2020-9352 since 02/23/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
By approaching the search of inurl:tools/developerConsoleOperations.jsp it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-150439, VDB-150438 and VDB-150436 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Xml entity expansionCWE: CWE-776
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
02/23/2020 🔍02/23/2020 🔍
02/23/2020 🔍
06/27/2024 🔍
Sources
Advisory: seclists.orgStatus: Not defined
CVE: CVE-2020-9352 (🔍)
GCVE (CVE): GCVE-0-2020-9352
GCVE (VulDB): GCVE-100-150437
See also: 🔍
Entry
Created: 02/23/2020 09:44Updated: 06/27/2024 01:16
Changes: 02/23/2020 09:44 (37), 02/23/2020 09:49 (17), 04/02/2024 11:07 (17), 06/27/2024 01:16 (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.