CVE-2017-14006
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGE Xeleris versions 1.0,1.1,2.1,3.0,3.1, medical imaging systems, all current versions are affected, these devices use default or hard-coded credentials. Successful exploitation of this vulnerability may allow a remote attacker to bypass authentication and gain access to the affected devices.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGE Xeleris medical imaging systems contain default or hard-coded credentials that allow remote unauthenticated attackers to bypass authentication and gain full access to the device. This is a critical vulnerability due to the combination of hardcoded credentials, remote exploitability, and the sensitive nature of medical imaging infrastructure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0= 1.1= 2.1= 3.0= 3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GE Xeleris installationInventory software on medical imaging workstations or servers, looking for GE Xeleris medical imaging application. Check installed programs list or scan for known Xeleris binary paths.Affected if GE Xeleris software is found in the environment
-
Determine the installed versionLocate the version information for the Xeleris installation. This is typically accessible through the application interface, about dialog, or system information panel within the software.Affected if The installed version matches 1.0, 1.1, 2.1, 3.0, or 3.1
-
Check if remote management interface is accessibleAssess network exposure of the Xeleris web interface or remote access service. Check firewall rules and networkACLs to determine if the management port is reachable from network segments outside the imaging device VLAN.Affected if The remote management interface is reachable from untrusted networks
-
Verify default credentials are in useAttempt to access the Xeleris interface using known default credentials, or examine authentication logs for evidence of default account usage. The vulnerability description indicates hardcoded credentials exist for remote authentication bypass.Affected if Default credentials are still active or the hardcoded credentials grant access
A defender is affected if they have GE Xeleris version 1.0, 1.1, 2.1, 3.0, or 3.1 installed AND the remote interface is network-accessible, as the hardcoded credentials allow unauthenticated remote access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately network-segment affected devices, block unauthorized access at perimeter controls, contact GE Healthcare for firmware updates that address the hardcoded credentials, and implement compensating controls such as strict access control lists until patches are available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data