CVE-2002-2445
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 Millennium MG, NC, and MyoSIGHT has a default password of (1) root.genie for the root user, (2) "service." for the service user, (3) admin.genie for the admin user, (4) reboot for the reboot user, and (5) shutdown for the shutdown 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 Millennium MG, NC, and MyoSIGHT medical imaging systems contain hardcoded default passwords for five system accounts (root, service, admin, reboot, shutdown). Attackers with network access can use these known credentials to authenticate and gain unauthorized access at varying privilege levels, potentially compromising patient data and system integrity.
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 versionsall versionsall 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.
-
Identify the medical imaging system productLocate the system information or product label on the device or check the system's About/Information panel to confirm the exact product name and versionAffected if The product is GE Healthcare Millennium MG, Millennium NC, or Millennium MyoSIGHT - all versions of these products are affected
-
Verify default system accounts existCheck the system account database (such as /etc/passwd or the device's user management interface) for the presence of accounts named: root, service, admin, reboot, shutdownAffected if Any of these five default accounts (root, service, admin, reboot, shutdown) are present on the system
-
Test default credentialsAttempt to authenticate using the known default passwords for each account. Default passwords for this CVE are publicly documented and should be looked up in the CVE reference. Common examples include: root:password, service:service, admin:admin, reboot:reboot, shutdown:shutdownAffected if Any of the default accounts accept their known default password, indicating the password was never changed from the manufacturer default
-
Check network accessibility to the deviceDetermine if the medical imaging system is accessible over the network (TCP/UDP ports, network interface status, firewall rules). Verify if untrusted network segments can reach the deviceAffected if The device is reachable from network segments accessible to untrusted users or systems, allowing remote exploitation of the default credentials
-
Review account privilege levelsExamine the privileges assigned to each default account (root, service, admin) to understand the potential impact of unauthorized accessAffected if The root, service, or admin accounts have elevated privileges and can be accessed using default credentials
A user is affected if they have a GE Healthcare Millennium MG, NC, or MyoSIGHT system where any of the five default accounts (root, service, admin, reboot, shutdown) still use their default 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 to strong, unique credentials per account, disable or rename accounts that are not required for operations, and implement network segmentation to restrict access to these medical devices.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2445 — 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-2002-2445 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