dbcve.org
Centricity Pacs IwApplication · Gehealthcare

CVE-2011-5324

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
The TeraRecon server, as used in GE Healthcare Centricity PACS-IW 3.7.3.7, 3.7.3.8, and possibly other versions, has a password of (1) shared for the shared user and (2) scan for the scan 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

The TeraRecon server component in GE Healthcare Centricity PACS-IW versions 3.7.3.7 and 3.7.3.8 (and possibly others) contains hardcoded default credentials. Two service accounts ('shared' and 'scan') use trivial passwords ('shared' and 'scan' respectively), allowing unauthenticated remote attackers to gain administrative access to the PACS imaging workstation infrastructure.

MitigationImmediately change the hardcoded passwords for the 'shared' and 'scan' accounts to strong, unique credentials on all affected TeraRecon server instances. Disable or remove these accounts if they are not required for legitimate operations. Implement network segmentation to limit exposure of the PACS infrastructure.

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. Identify Centricity PACS-IW version
    Locate the installed GE Healthcare Centricity PACS-IW version information. Check system inventory, software registry, or the About/Version dialog within the PACS client interface. Compare the version number to 3.7.3.7 or 3.7.3.8.
    Affected if The installed version matches exactly 3.7.3.7 or 3.7.3.8 (or falls within an unconfirmed range including these versions)
  2. Confirm TeraRecon server component presence
    Identify whether the TeraRecon server component is deployed in the environment. Check for TeraRecon server processes, services, or installed software modules on the PACS infrastructure. Look for TeraRecon-related executables, services, or documentation.
    Affected if The TeraRecon server component is installed as part of the PACS infrastructure
  3. Locate service accounts on the system
    Enumerate user accounts on the TeraRecon server system. Use account management tools (e.g., 'net user' on Windows, 'cat /etc/passwd' on Linux, or Active Directory Users and Computers) to list all local or domain accounts. Look specifically for accounts named 'shared' and 'scan'.
    Affected if Accounts named 'shared' and 'scan' exist on the system
  4. Verify default password status for 'shared' account
    Attempt to authenticate using the 'shared' account with password 'shared', or examine password policy/compliance reports to determine if this account uses its default password. Check if password matches username (trivial password).
    Affected if The 'shared' account password is set to 'shared' or another trivial/default password
  5. Verify default password status for 'scan' account
    Attempt to authenticate using the 'scan' account with password 'scan', or examine password policy/compliance reports to determine if this account uses its default password. Check if password matches username (trivial password).
    Affected if The 'scan' account password is set to 'scan' or another trivial/default password

You are affected if your environment runs GE Healthcare Centricity PACS-IW version 3.7.3.7 or 3.7.3.8 with the TeraRecon server component, and the 'shared' and/or 'scan' accounts retain their default trivial passwords ('shared' and 'scan' respectively).

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 hardcoded passwords for the 'shared' and 'scan' accounts to strong, unique credentials on all affected TeraRecon server instances. Disable or remove these accounts if they are not required for legitimate operations. Implement network segmentation to limit exposure of the PACS infrastructure.

Fix this in Centricity Pacs Iw 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-5324 — 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-5324 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