CVE-2012-6693
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 4.0 Server has a default password of (1) nasro for the nasro (ReadOnly) user and (2) nasrw for the nasrw (Read/Write) user, 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 confidenceGE Healthcare Centricity PACS 4.0 Server ships with hardcoded default credentials. The 'nasro' account (ReadOnly) and 'nasrw' account (Read/Write) use their respective account names as passwords. An attacker with network access to the PACS server can authenticate using these default credentials to gain unauthorized access to the medical imaging system, potentially exposing sensitive patient data or disrupting healthcare operations.
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.0CVSS 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.
-
Confirm Centricity PACS Server versionLocate and inspect the installed GE Healthcare Centricity PACS Server version on your system. This is typically available through the application itself, system inventory, or product documentation shipped with the software.Affected if The installed version is exactly 4.0 (Gehealthcare Centricity Pacs Server = 4.0)
-
Verify if default accounts existCheck whether the 'nasro' (ReadOnly) and 'nasrw' (Read/Write) user accounts are present in your Centricity PACS Server user database or authentication system. Consult your system administration guide for user account enumeration methods.Affected if The nasro and/or nasrw accounts exist in the PACS authentication system
-
Test default credentialsAttempt to authenticate to the PACS server using 'nasro' as both username and password, and separately 'nasrw' as both username and password. This requires access to the PACS authentication interface or network service.Affected if Either 'nasro' or 'nasrw' authenticates successfully using their respective account names as passwords
-
Assess network exposureDetermine if the PACS server is accessible over the network from locations outside your trusted internal network. Check firewall rules and network segmentation surrounding the PACS server.Affected if The PACS server is reachable from untrusted network segments or the internet
Your environment is affected if you run Centricity PACS Server version 4.0 and the nasro/nasrw accounts still use their default passwords and are accessible over the network.
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.
dbcve · scopedImmediately change the default passwords for both the nasro and nasrw accounts to strong, unique passwords following organizational policy, or disable these accounts if not required. Implement network segmentation to limit exposure of the PACS server and enforce multi-factor authentication for administrative access.
Contact GE Healthcare for information on Centricity PACS version updates or patches that may address default credential vulnerabilities
- Change the default password for the nasro (ReadOnly) user from 'nasro' to a strong, unique password immediately upon first login
- Change the default password for the nasrw (Read/Write) user from 'nasrw' to a strong, unique password immediately upon first login
- If the application does not allow password changes through its administrative interface, contact GE Healthcare technical support for a patch or workaround
- Review all user accounts on the system and ensure no other default credentials are in use
- Document the new passwords in a secure password manager rather than storing them in plaintext
- Verify that the new passwords meet your organization's password complexity requirements
- After changing passwords, audit access logs for any unauthorized access attempts using the default credentials
- Contact GE Healthcare to confirm whether a firmware or software update is available that addresses this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6693 — 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-6693 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