dbcve.org
Centricity Analytics ServerApplication · Gehealthcare

CVE-2011-5322

HIGH · 10.0 CVSS v2.0 Published 2015-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GE Healthcare Centricity Analytics Server 1.1 contains multiple hardcoded default passwords for SQL Server and Webmin interface accounts. The 'sa' user has password 'V0yag3r', analyst and ccg users share 'G3car3s', viewer user uses 'V0yag3r', and geservice uses 'geservice'. These credentials provide unauthenticated attackers with full database and administrative access.

MitigationImmediately change all default passwords listed in the advisory to strong, unique values. Disable unused default accounts, especially the 'sa' and 'geservice' accounts. Implement a credential management policy to prevent future hardcoded credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Centricity Analytics ServerApplication
Affected:= 1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the installed version is Centricity Analytics Server 1.1
    Check the product version through the application's About section, Windows Add/Remove Programs, or by querying the installed software registry key (HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall). Compare the version displayed against 1.1.
    Affected if The installed version is exactly 1.1
  2. Test SQL Server 'sa' account for hardcoded password
    Attempt to authenticate to the SQL Server instance used by Centricity Analytics using the 'sa' account with password 'V0yag3r'. This can be done via SQL Server Management Studio, sqlcmd, or a connection string test.
    Affected if Authentication succeeds with username 'sa' and password 'V0yag3r'
  3. Test 'analyst' and 'ccg' database accounts for hardcoded password
    Attempt to authenticate to the SQL Server instance using accounts 'analyst' and 'ccg' both with password 'G3car3s'. Check both accounts individually.
    Affected if Authentication succeeds with either 'analyst'/'G3car3s' or 'ccg'/'G3car3s' credentials
  4. Test 'viewer' account for hardcoded password
    Attempt to authenticate to the application or SQL Server using the 'viewer' account with password 'V0yag3r'.
    Affected if Authentication succeeds with username 'viewer' and password 'V0yag3r'
  5. Test 'geservice' account for hardcoded password
    Attempt to authenticate to the Webmin administrative interface (typically port 10000) or SQL Server using the 'geservice' account with password 'geservice'.
    Affected if Authentication succeeds with username 'geservice' and password 'geservice'

If the product version is 1.1 and any of the default accounts (sa, analyst, ccg, viewer, geservice) can be accessed using their respective hardcoded passwords (V0yag3r, G3car3s, geservice), the environment is affected by CVE-2011-5322.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change all default passwords listed in the advisory to strong, unique values. Disable unused default accounts, especially the 'sa' and 'geservice' accounts. Implement a credential management policy to prevent future hardcoded credentials.

Fix this in Centricity Analytics Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-5322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-5322 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data