CVE-2011-5322: GE Healthcare Centricity Analytics Server 1.1 has a default password of (1) V0yag3r for the SQL Server sa user
CVE-2011-5322 is a high-severity flaw (CVSS 10.0) affecting centricity analytics server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 10.0 (High) |
| EPSS exploit chance | 1.7% (top 23%) |
| CISA exploited list | No |
| Weakness | CWE-255 |
| Published | 2015-08-04 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2011-5322?
centricity analytics server: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2011-5322 being exploited?
CVE-2011-5322 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2011-5322 affect?
CVE-2011-5322 affects centricity analytics server. Severity is high (CVSS 10.0). 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 geser
How urgent is CVE-2011-5322?
Priority 54/100. Critical severity
Software pages
Microsoft SQL Server vulnerabilities