CVE-2013-7442
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 · uneditedGE Healthcare Centricity PACS Workstation 4.0 and 4.0.1 has a password of (1) CANal1 for the Administrator user and (2) iis for the IIS user, which has unspecified impact and attack vectors related to TimbuktuPro. NOTE: it is not clear whether this password is default, hardcoded, or dependent on another system or product that requires it.
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 confidenceGE Healthcare Centricity PACS Workstation versions 4.0 and 4.0.1 contain hardcoded/default credentials with password 'CANal1' assigned to the Administrator user and 'iis' assigned to the IIS user. These credentials can be exploited to gain unauthorized access to the workstation, potentially allowing attackers to access sensitive medical imaging data or pivot to other systems.
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= 4.0= 4.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if GE Healthcare Centricity PACS Workstation is installedCheck the system for the presence of GE Healthcare Centricity PACS Workstation software. This may be listed in Add/Remove Programs (Windows) or via system inventory tools.Affected if The software is present on the system
-
Determine the installed version of Centricity PACS WorkstationLocate and examine the version information for the installed Centricity PACS Workstation software. This may be found in the program properties, installation directory, or registry.Affected if The installed version is 4.0 or 4.0.1 specifically
-
Verify if default Administrator account exists with hardcoded passwordCheck system accounts for an Administrator account configured with the password 'CANal1'. On affected systems, this hardcoded credential is present by default.Affected if The Administrator account is configured with password 'CANal1' on a version 4.0 or 4.0.1 installation
-
Verify if default IIS user account exists with hardcoded passwordCheck system accounts for an IIS user account configured with the password 'iis'. On affected systems, this hardcoded credential is present by default.Affected if The IIS user account is configured with password 'iis' on a version 4.0 or 4.0.1 installation
The environment is affected if GE Healthcare Centricity PACS Workstation version 4.0 or 4.0.1 is installed and contains the hardcoded credentials 'CANal1' for Administrator or 'iis' for the IIS user.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately change the hardcoded passwords to strong, unique credentials on all affected workstations and implement proper password management policies. Verify that these credentials are not used on any other systems or legacy components like TimbuktuPro.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-7442 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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