# CVE-2006-7253: Hardcoded credentials in n/a

> GE Healthcare Infinia II devices contain hardcoded default passwords for multiple user accounts, allowing unauthorized access and potential privilege escalation.

- **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:** 7 Aug 2024
- **Also known as:** GHSA-xpj7-qrq5-7w9m

## What is CVE-2006-7253?

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

### Official description

GE Healthcare Infinia II has a default password of (1) infinia for the infinia user, (2) #bigguy1 for the acqservice user, (3) dont4get2 for the Administrator user, (4) #bigguy1 for the emergency user, and (5) 2Bfamous for the InfiniaAdmin user, which has unspecified impact and attack vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2006-7253?

It affects 1 product.


Products: Gehealthcare Infinia Ii.

## How do I fix CVE-2006-7253?

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

## Is CVE-2006-7253 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7253 and fix it if it is affected.

What it is: CVE-2006-7253 is a critical vulnerability in n/a, published on 4 Aug 2015. 
Exploitation: There is no known exploitation of CVE-2006-7253 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-2006-7253/ (Markdown: https://insights.sbomify.com/CVE-2006-7253/index.md)
```

## Sources

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

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