# CVE-2017-14002: Hardcoded credentials in GE Infinia

> Remote attackers can bypass authentication and gain access to GE Infinia medical imaging systems using hard-coded credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 20 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vc9p-mffq-wv28

## What is CVE-2017-14002?

CVE-2017-14002 is a critical vulnerability in GE Infinia, published on 20 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GE Infinia/Infinia with Hawkeye 4 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Ge Infinia Hawkeye 4 Firmware.

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

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

## Is CVE-2017-14002 being exploited?

There is no known exploitation of CVE-2017-14002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14002 is a critical vulnerability in GE Infinia, published on 20 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14002 in the wild and no public exploit code.

Affected product: GE Infinia. 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-14002/ (Markdown: https://insights.sbomify.com/CVE-2017-14002/index.md)
```

## Sources

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

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