# CVE-2017-11165: Information disclosure in n/a

> Remote attackers can obtain sensitive credentials and configuration data by requesting a specific URI on dataTaker DT80 dEX devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h4fr-cprr-q23r

## What is CVE-2017-11165?

CVE-2017-11165 is a critical vulnerability in n/a, published on 12 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-11165?

It affects 1 product.


Products: Thermofisher Dt80 Dex Firmware.

## How do I fix CVE-2017-11165?

No fix has been published for CVE-2017-11165 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-11165 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11165 exists.

Public exploit code:

- DataTaker DT80 dEX 1.50.012 - Information Disclosure (exploitdb)
- DataTaker DT80 dEX 1.50.012 - Information Disclosure (nuclei): http/cves/2017/CVE-2017-11165.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11165 and fix it if it is affected.

What it is: CVE-2017-11165 is a critical vulnerability in n/a, published on 12 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11165 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11165/ (Markdown: https://insights.sbomify.com/CVE-2017-11165/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11165
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11165
- OSV: https://osv.dev/vulnerability/CVE-2017-11165

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11165/
Summaries are generated and may contain mistakes; the official description above is the record.