dbcve.org
Entegra P\&rApplication · Gehealthcare

CVE-2001-1594

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 eNTEGRA P&R has a password of (1) entegra for the entegra user, (2) passme for the super user of the Polestar/Polestar-i Starlink 4 upgrade, (3) 0 for the entegra user of the Codonics printer FTP service, (4) eNTEGRA for the eNTEGRA P&R user account, (5) insite for the WinVNC Login, and possibly other accounts, 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 confidence

GE Healthcare eNTEGRA P&R medical imaging workstation contains multiple hardcoded/default credentials across various services and accounts including VNC (insite), FTP (0), and multiple user accounts (entegra, passme, eNTEGRA). The static nature of these passwords allows unauthenticated remote attackers to gain privileged access to the system and its connected services.

MitigationImmediately change all known default credentials to strong, unique passwords; disable unused services (particularly VNC and anonymous FTP); review and disable any unnecessary accounts; contact GE Healthcare for official patch or guidance given this is a medical device.

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
Entegra P\&rApplication
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 if GE Healthcare eNTEGRA P&R is installed
    Check system for presence of eNTEGRA P&R software - look for installation directory (commonly under C:\Program Files\GE Healthcare\entegra or similar path on Windows systems), check installed programs list, or query for GE Healthcare services.
    Affected if The eNTEGRA P&R application or related services are found on the system.
  2. Check if VNC service is enabled
    Review running services for VNC-related processes (such as RealVNC, TightVNC, or proprietary VNC), check for port 5900 listening, and inspect startup items for VNC components.
    Affected if VNC service is running and accessible on the network.
  3. Check if FTP service is enabled
    Query for FTP server processes, check for port 21 listening, review any FTP server configuration files, and verify if anonymous FTP access is permitted.
    Affected if FTP service is running and accepts connections.
  4. Inspect for default user accounts
    Check local user accounts or application-specific user databases for existence of accounts named: entegra, passme, eNTEGRA, or insite. On Windows check Computer Management > Local Users and Groups; on Linux check /etc/passwd.
    Affected if Any of the known default accounts (entegra, passme, eNTEGRA, insite) exist on the system.
  5. Verify credential status for known default accounts
    Attempt to authenticate using the known default credentials if accounts exist, or review application configuration files for hardcoded password strings (look for passwords: insite, 0, passme in config files).
    Affected if Default credentials still function or hardcoded passwords are found in configuration files.

A system is affected if GE Healthcare eNTEGRA P&R is installed with VNC or FTP services enabled, or if any default accounts (entegra, passme, eNTEGRA, insite) with their known default passwords are present and accessible.

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

Immediately change all known default credentials to strong, unique passwords; disable unused services (particularly VNC and anonymous FTP); review and disable any unnecessary accounts; contact GE Healthcare for official patch or guidance given this is a medical device.

Fix this in Entegra P\&r Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2001-1594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2001-1594 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