CIMTechniques CIMScan 6.0/6.1/6.2 SOAP WSDL Parser GetSqlData SQL sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CIMTechniques CIMScan 6.0/6.1/6.2. It has been rated as critical. The affected element is the function GetSqlData of the component SOAP WSDL Parser. Performing a manipulation as part of SQL results in sql injection.
This vulnerability was named CVE-2018-16803. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in CIMTechniques CIMScan 6.0/6.1/6.2. It has been classified as critical. This affects the function GetSqlData of the component SOAP WSDL Parser. The manipulation as part of a SQL leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In CIMTechniques CIMScan 6.x through 6.2, the SOAP WSDL parser allows attackers to execute SQL code.
The bug was discovered 01/10/2019. The weakness was presented 01/10/2019 by Joël Aviad Ossi (websecnl) with WebSec B.V. as confirmed advisory (hackerone) via DoD Cyber Crime Center (DC3). It is possible to read the advisory at hackerone.com. This vulnerability is uniquely identified as CVE-2018-16803 since 09/10/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
It is declared as highly functional.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
Researcher Base Score: 8.0
Researcher Vector: 🔍
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: 🔍
Researcher Base Score: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
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
09/10/2018 🔍01/10/2019 🔍
01/10/2019 🔍
01/10/2019 🔍
01/11/2019 🔍
09/07/2020 🔍
Sources
Advisory: hackerone.comResearcher: Joël Aviad Ossi (websecnl)
Organization: WebSec B.V.
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-16803 (🔍)
GCVE (CVE): GCVE-0-2018-16803
GCVE (VulDB): GCVE-100-129003
Entry
Created: 01/11/2019 08:07Updated: 09/07/2020 09:53
Changes: 01/11/2019 08:07 (61), 01/17/2019 10:10 (2), 01/17/2019 10:11 (2), 01/17/2019 10:12 (4), 01/17/2019 10:13 (3), 01/17/2019 10:14 (1), 01/22/2019 08:18 (3), 05/04/2020 10:53 (1), 09/07/2020 09:53 (4)
Complete: 🔍
Committer: websecnl
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.