# CVE-2011-5322: Hardcoded credentials in n/a

> GE Healthcare Centricity Analytics Server uses hardcoded default passwords for SQL and Webmin 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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2015
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5cwq-frjr-7c95

## What is CVE-2011-5322?

CVE-2011-5322 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 Analytics Server 1.1 has a default password of (1) V0yag3r for the SQL Server sa user, (2) G3car3s for the analyst user, (3) G3car3s for the ccg user, (4) V0yag3r for the viewer user, and (5) geservice for the geservice user in the Webmin interface, which has unspecified impact and attack vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2011-5322?

It affects 1 product.


Products: Gehealthcare Centricity Analytics Server.

## How do I fix CVE-2011-5322?

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

## Is CVE-2011-5322 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5322 and fix it if it is affected.

What it is: CVE-2011-5322 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-2011-5322 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-2011-5322/ (Markdown: https://insights.sbomify.com/CVE-2011-5322/index.md)
```

## Sources

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

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