CVE-2012-6695
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 ddpadmin for the ddpadmin 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 · high confidenceGE Healthcare Centricity PACS Workstation versions 4.0 and 4.0.1 contain a hardcoded/default password 'ddpadmin' for the ddpadmin user account, allowing unauthorized administrative access to the medical imaging system.
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 installed version of GE Healthcare Centricity PACS WorkstationCheck the program's About or Help menu, or inspect the installation directory for version information files. On Windows, check Add/Remove Programs or the program's executable properties.Affected if The installed version is exactly 4.0 or 4.0.1
-
Verify the ddpadmin user account existsAccess the user management or account administration panel within the Centricity PACS Workstation application, or review the system's local user accounts if the application uses OS-level authentication.Affected if The ddpadmin account is present in the system
-
Test authentication with the default passwordAttempt to log in using the username 'ddpadmin' and the password 'ddpadmin' through the application's login interface or any administrative access point.Affected if Login succeeds with these credentials, confirming the default password has not been changed
-
Review account password policy and last change dateInspect the application's user account settings, security configuration, or audit logs to determine when the ddpadmin password was last changed and whether it complies with password policy requirements.Affected if The password has never been changed from default or was never set to meet strong password requirements
You are affected if GE Healthcare Centricity PACS Workstation version 4.0 or 4.0.1 is installed and the ddpadmin account can be accessed using the default password 'ddpadmin'.
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 dataChange the default password immediately to a strong, unique credential. Contact GE Healthcare for a formal patch or guidance on proper account management, and audit the system for unauthorized access since the vulnerability was disclosed.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6695 — 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-2012-6695 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