Millennium Mg FirmwareOperating system · Gehealthcare

CVE-2002-2446

HIGH · 10.0 CVSS v2.0 Published 2015-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
GE Healthcare Millennium MG, NC, and MyoSIGHT has a password of insite.genieacq for the insite account that cannot be changed without disabling product functionality for remote InSite support, 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 · moderate confidence

Hardcoded credentials (username: insite, password: insite.genieacq) exist in GE Healthcare Millennium MG, NC, and MyoSIGHT medical imaging systems. The password cannot be changed without disabling remote InSite support functionality, creating a situation where the system cannot be secured without losing vendor support capabilities.

MitigationSince the password cannot be changed without breaking functionality, implement compensating controls such as network segmentation to isolate the device, restrict access to the InSite support interface via firewall rules, and contact GE Healthcare for vendor-specific guidance or firmware updates that may address this vulnerability.

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
Millennium Mg FirmwareOperating system
Affected:all versions
Millennium Myosight FirmwareOperating system
Affected:all versions
Millennium Nc FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the medical imaging system model
    Locate the system label, boot screen, or administrative interface to confirm the device is a GE Healthcare Millennium MG, Millennium NC, or Millennium MyoSIGHT system
    Affected if The system is any of these three models running any firmware version
  2. Determine if InSite remote support is enabled
    Check the system configuration settings, service documentation, or network listening services for evidence of the InSite support interface being active. Look for ports or services associated with remote GE Healthcare support access
    Affected if InSite remote support functionality is enabled or accessible on the system
  3. Assess network exposure of the InSite service
    Review network firewall rules, internal network segmentation, and external access controls to determine if the InSite support interface is reachable from network segments other than isolated vendor support networks
    Affected if The InSite support interface is reachable from networks beyond isolated vendor support channels
  4. Verify if default support credentials are in use
    Examine any accessible support configuration files, service logs, or vendor documentation that may confirm whether the default insite username and insite.genieacq password pair are still configured for the InSite support functionality
    Affected if The default hardcoded credentials (insite/insite.genieacq) are confirmed to be active for the InSite support service

A user is affected if they operate a GE Healthcare Millennium MG, NC, or MyoSIGHT system with InSite remote support enabled and accessible, where the hardcoded credentials cannot be changed without losing vendor support functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the password cannot be changed without breaking functionality, implement compensating controls such as network segmentation to isolate the device, restrict access to the InSite support interface via firewall rules, and contact GE Healthcare for vendor-specific guidance or firmware updates that may address this vulnerability.

Fix this in Millennium Mg Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing8.0 h
  • Review / QA4.0 h
44.0 hours of engineering $7,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,672.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2446 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-2446 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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