# CVE-2012-6693: Hardcoded credentials in n/a

> GE Healthcare Centricity PACS Server uses default credentials for read-only and read-write users, allowing unauthorized access to medical imaging data.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p9vx-9vqh-hv34

## What is CVE-2012-6693?

CVE-2012-6693 is a critical vulnerability in n/a, published on 4 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GE Healthcare Centricity PACS 4.0 Server has a default password of (1) nasro for the nasro (ReadOnly) user and (2) nasrw for the nasrw (Read/Write) user, which has unspecified impact and attack vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2012-6693?

It affects 1 product.


Products: Gehealthcare Centricity Pacs Server.

## How do I fix CVE-2012-6693?

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

## Is CVE-2012-6693 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6693 and fix it if it is affected.

What it is: CVE-2012-6693 is a critical vulnerability in n/a, published on 4 Aug 2015. 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-2012-6693 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-2012-6693/ (Markdown: https://insights.sbomify.com/CVE-2012-6693/index.md)
```

## Sources

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

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