How severe is CVE-2017-11165?

CVE-2017-11165 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-11165?

Affected package information for CVE-2017-11165 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-11165?

No fixed version has been published for CVE-2017-11165 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2017-11165 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2017-11165, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-11165?

CVE-2017-11165 has an EPSS (Exploit Prediction Scoring System) score of 91.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2017-11165?

CVE-2017-11165 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2017-11165?

CVE-2017-11165 affects thermofisher dt80 dex firmware (1 version, e.g. 1.50.012). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2017-11165?

A Nuclei detection template exists for CVE-2017-11165, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-11165 published, and has it been updated?

CVE-2017-11165 was published on July 12, 2017 and was last updated on April 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2017-11165

CRITICAL

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.

Published

Jul 12, 2017

Updated

Apr 30, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

91.5%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

1 product · 1 configurations

dt80 dex firmwarethermofisher

1 version

1.50.012

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-42313webappshardware

DataTaker DT80 dEX 1.50.012 - Information Disclosure

by Nassim Asrir · Jul 11, 2017

Exploit-DB Source

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2017-11165 in your stack?

O3 detects CVE-2017-11165 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works