dbcve.org
Centricity Clinical Archive Audit Trail RepositoryApplication · Gehealthcare

CVE-2014-9736

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 Clinical Archive Audit Trail Repository has a default password of initinit for the (1) SSL key manager and (2) server keystore; (3) keystore_password for the server truststore; and atna for the (4) primary storage database and (5) archive storage database, 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 Clinical Archive Audit Trail Repository contains multiple hardcoded default passwords: 'initinit' for SSL key manager and server keystore, 'keystore_password' for server truststore, and 'atna' for both primary and archive storage databases. These credentials cannot be changed through normal configuration and provide full access to sensitive clinical data, encrypted communications, and database storage.

MitigationImmediately change all default passwords on all affected components (SSL key manager, keystore, truststore, and both databases) to strong, unique passwords following vendor guidance, and implement a credential management policy to prevent future exposure.

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 Clinical Archive Audit Trail RepositoryApplication
Affected:all versions

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 if GE Healthcare Centricity Clinical Archive Audit Trail Repository is installed
    Check your system for the presence of GE Healthcare Centricity Clinical Archive Audit Trail Repository software. Look in standard application installation directories or use system inventory tools to enumerate installed healthcare software.
    Affected if The software is present on the system, indicating the environment contains this vulnerable component.
  2. Locate SSL keystore configuration files
    Search for configuration files related to SSL key manager and keystore settings. Look for files containing references to keystore, keymanager, or SSL configuration within the application directory structure.
    Affected if Configuration files contain the default password 'initinit' for SSL key manager or server keystore access.
  3. Locate truststore configuration files
    Search for configuration files related to server truststore settings. Look for files containing references to truststore or certificate validation within the application directory structure.
    Affected if Configuration files contain the default password 'keystore_password' for server truststore access.
  4. Locate database configuration files
    Search for configuration files related to primary and archive storage database connections. Look for files containing database connection strings or credential storage within the application directory structure.
    Affected if Configuration files contain the default password 'atna' for primary or archive storage database connections.
  5. Verify password change capability
    Attempt to change the passwords through the product's normal administration interface or configuration tools. Note whether the interface allows modification of these specific credentials.
    Affected if The passwords cannot be changed through normal configuration, confirming the hardcoded credential vulnerability.

If GE Healthcare Centricity Clinical Archive Audit Trail Repository is installed and any configuration files contain the default passwords 'initinit', 'keystore_password', or 'atna', the environment is affected by this vulnerability.

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 on all affected components (SSL key manager, keystore, truststore, and both databases) to strong, unique passwords following vendor guidance, and implement a credential management policy to prevent future exposure.

Fix this in Centricity Clinical Archive Audit Trail Repository Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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