dbcve.org
Centricity Pacs IwApplication · Gehealthcare

CVE-2011-5323

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 PACS-IW 3.7.3.7, 3.7.3.8, and possibly other versions has a password of A11enda1e for the sa SQL server user, which has unspecified impact and attack vectors. NOTE: it is not clear whether this password is default, hardcoded, or dependent on another system or product that requires a fixed value.

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 · moderate confidence

GE Healthcare Centricity PACS-IW contains a hardcoded password 'A11enda1e' for the SQL Server 'sa' administrative account. This hardcoded credential is embedded in the software, allowing attackers who discover it to gain full administrative access to the database with complete control over all stored data and potentially the application itself.

MitigationImmediately change the 'sa' password to a strong, unique value and disable the 'sa' account if not required; implement network segmentation to limit database exposure; contact GE Healthcare for an official patch and guidance on secure configuration.

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 Pacs IwApplication
Affected:= 3.7.3.7= 3.7.3.8

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. Check installed product version
    Identify the installed version of GE Healthcare Centricity PACS-IW by examining application metadata, installer records, or system information about the software. Compare your version against 3.7.3.7 and 3.7.3.8.
    Affected if Your installed version is exactly 3.7.3.7 or 3.7.3.8
  2. Search for hardcoded password in application files
    Search all configuration files, DLL files, and application binaries within the Centricity PACS-IW installation directory for the string 'A11enda1e'. Use file content search tools to scan both plain text and binary files.
    Affected if The password string 'A11enda1e' is found embedded in any application file or configuration
  3. Inspect database connection configurations
    Examine database connection strings, config files, and application settings that define how the software connects to the SQL Server database. Look for hardcoded credentials in connection parameters.
    Affected if A connection string contains the hardcoded 'sa' account with password 'A11enda1e'
  4. Test SQL Server authentication with hardcoded credential
    Attempt to authenticate to the SQL Server instance used by Centricity PACS-IW using the 'sa' account and password 'A11enda1e'. This requires network or local access to the database server.
    Affected if Authentication succeeds with these credentials, confirming the hardcoded password is active
  5. Verify sa account status
    Check the status of the SQL Server 'sa' account in the database to determine if it is enabled and whether it is using the hardcoded password.
    Affected if The 'sa' account is enabled and accessible using password 'A11enda1e'

You are affected if your Centricity PACS-IW version is 3.7.3.7 or 3.7.3.8 AND the hardcoded password 'A11enda1e' is present in your environment and grants administrative access to the SQL Server database.

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 the 'sa' password to a strong, unique value and disable the 'sa' account if not required; implement network segmentation to limit database exposure; contact GE Healthcare for an official patch and guidance on secure configuration.

Fix this in Centricity Pacs Iw Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-5323 — 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-5323 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