# CVE-2014-7233: Hardcoded credentials in n/a

> GE Healthcare Precision THUNIS-800+ devices contain hardcoded default passwords for system utilities and setup menus, potentially allowing unauthorized access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8j65-jq8v-855x

## What is CVE-2014-7233?

CVE-2014-7233 is a critical vulnerability in n/a, published on 4 Aug 2015. 

### Official description

GE Healthcare Precision THUNIS-800+ has a default password of (1) 1973 for the factory default System Utilities menu, (2) TH8740 for installation using TH8740_122_Setup.exe, (3) hrml for "Setup and Activation" using DSASetup, and (4) an empty string for Shutter Configuration, which has unspecified impact and attack vectors.  NOTE: since these passwords appear to be used to access functionality during installation, this issue might not cross privilege boundaries and might not be a vulnerability.

Weakness: CWE-255

## Which versions are affected by CVE-2014-7233?

It affects 1 product.


Products: Gehealthcare Precision Thunis-800\+.

## How do I fix CVE-2014-7233?

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

## Is CVE-2014-7233 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7233 and fix it if it is affected.

What it is: CVE-2014-7233 is a critical vulnerability in n/a, published on 4 Aug 2015. 
Exploitation: There is no known exploitation of CVE-2014-7233 in the wild and no public exploit code.

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-2014-7233/ (Markdown: https://insights.sbomify.com/CVE-2014-7233/index.md)
```

## Sources

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

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