dataTaker DT80 dEX 1.50.012 /services/getFile.cmd userfile Config information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in dataTaker DT80 dEX 1.50.012. This impacts an unknown function of the file /services/getFile.cmd. The manipulation of the argument userfile with the input config.xml as part of Request leads to information disclosure (Config).
This vulnerability is referenced as CVE-2017-11165. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in dataTaker DT80 dEX 1.50.012. This issue affects an unknown functionality of the file /services/getFile.cmd. The manipulation of the argument userfile with the input value config.xml leads to a information disclosure vulnerability (Config). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
dataTaker DT80 dEX 1.50.012 allows remote attackers to obtain sensitive credential and configuration information via a direct request for the /services/getFile.cmd?userfile=config.xml URI.
The bug was discovered 07/12/2017. The weakness was published 07/12/2017 (Website). It is possible to read the advisory at packetstormsecurity.com. The identification of this vulnerability is CVE-2017-11165 since 07/10/2017. 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 as well as a public exploit are known. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (42313). 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: 7.6VulDB Meta Temp Score: 7.3
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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
Name: ConfigClass: Information disclosure / Config
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/10/2017 🔍07/12/2017 🔍
07/12/2017 🔍
07/12/2017 🔍
07/12/2017 🔍
01/16/2026 🔍
Sources
Advisory: 143328Status: Not defined
CVE: CVE-2017-11165 (🔍)
GCVE (CVE): GCVE-0-2017-11165
GCVE (VulDB): GCVE-100-103475
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/12/2017 23:26Updated: 01/16/2026 20:50
Changes: 07/12/2017 23:26 (61), 10/25/2019 09:43 (4), 12/12/2022 11:25 (4), 06/13/2024 07:28 (14), 01/16/2026 20:50 (5)
Complete: 🔍
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.