# CVE-2010-5307: Hardcoded credentials in n/a

> Hardcoded credentials in GE Healthcare Optima MR360 allow unauthorized access to the HIPAA configuration interface, posing a risk to medical data security.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2015
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fx97-phwp-c88v

## What is CVE-2010-5307?

CVE-2010-5307 is a critical vulnerability in n/a, published on 4 Aug 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The HIPAA configuration interface in GE Healthcare Optima MR360 has a password of (1) operator for the root account, (2) adw2.0 for the admin account, and (3) adw2.0 for the sdc account, which has unspecified impact and attack vectors.  NOTE: it is not clear whether these passwords are default, hardcoded, or dependent on another system or product that requires a fixed value.

Weakness: CWE-255

## Which versions are affected by CVE-2010-5307?

It affects 1 product.


Products: Gehealthcare Optima Mr360 Firmware.

## How do I fix CVE-2010-5307?

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

## Is CVE-2010-5307 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5308](https://insights.sbomify.com/CVE-2010-5308/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5307 and fix it if it is affected.

What it is: CVE-2010-5307 is a critical vulnerability in n/a, published on 4 Aug 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-5307 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-2010-5307/ (Markdown: https://insights.sbomify.com/CVE-2010-5307/index.md)
```

## Sources

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

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