# CVE-2010-5308: Auth bypass in n/a

> Physically proximate attackers can bypass authentication via the emergency login screen to access the medical imaging system.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Aug 2015
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fp52-46r3-jwx9

## What is CVE-2010-5308?

CVE-2010-5308 is a critical authentication bypass vulnerability in n/a, published on 4 Aug 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

GE Healthcare Optima MR360 does not require authentication for the HIPAA emergency login procedure, which allows physically proximate users to gain access via an arbitrary username in the Emergency Login screen.  NOTE: this might not qualify for inclusion in CVE if unauthenticated emergency access is part of the intended security policy of the product, can be controlled by the system administrator, and is not enabled by default.

Weakness: CWE-255

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

It affects 1 product.


Products: Gehealthcare Optima Mr360 Firmware.

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

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

## Is CVE-2010-5308 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5307](https://insights.sbomify.com/CVE-2010-5307/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-5308 is a critical authentication bypass vulnerability in n/a, published on 4 Aug 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-5308 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-5308/ (Markdown: https://insights.sbomify.com/CVE-2010-5308/index.md)
```

## Sources

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

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