CVE-2006-7253
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 Infinia II has a default password of (1) infinia for the infinia user, (2) #bigguy1 for the acqservice user, (3) dont4get2 for the Administrator user, (4) #bigguy1 for the emergency user, and (5) 2Bfamous for the InfiniaAdmin 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 Infinia II gamma camera systems ship with five hardcoded default passwords across multiple accounts (infinia, acqservice, Administrator, emergency, InfiniaAdmin). These well-known credentials can be used by unauthorized attackers to gain remote access to the 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 dataall versionsCVSS 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 the system is a GE Healthcare Infinia II gamma cameraCheck system identification, inventory records, or device labeling to verify the model is Infinia II. These are nuclear medicine gamma cameras used for diagnostic imaging.Affected if The system is confirmed to be a GE Healthcare Infinia II gamma camera
-
Identify active user accounts on the systemAccess the system locally or via available administrative interfaces to list user accounts. Look for accounts named: infinia, acqservice, Administrator, emergency, InfiniaAdmin.Affected if Any of these five default accounts (infinia, acqservice, Administrator, emergency, InfiniaAdmin) exist on the system
-
Test default credentials against identified accountsAttempt to authenticate using the account names with their default password (typically matching the username, such as 'infinia' for the infinia account). Document whether authentication succeeds without password changes.Affected if Any default account accepts its well-known default password without modification
-
Check network exposure of the deviceIdentify IP address and determine if the device is reachable from network segments outside the local medical device network. Review firewall rules and network segmentation around the device.Affected if The Infinia II device is accessible from network segments beyond its isolated medical device network
-
Determine if remote access services are enabledCheck if remote access services (RDP, Telnet, VNC, SSH, or vendor-specific remote service ports) are enabled and listening on the device network interfaces.Affected if Remote access services are enabled and accessible on the device
A system is affected if it is a GE Healthcare Infinia II gamma camera where any of the five default accounts still use their hardcoded passwords and the device is network-accessible to potential attackers.
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 all default passwords on affected systems per vendor guidance, disable unused accounts, and isolate the medical devices on restricted network segments to prevent external exploitation.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-7253 — 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-2006-7253 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