dbcve.org
Discovery VhApplication · Gehealthcare

CVE-2003-1603

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 Discovery VH has a default password of (1) interfile for the ftpclient user of the Interfile server or (2) "2" for the LOCAL user of the FTP server for the Codonics printer, 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 confidence

GE Healthcare Discovery VH medical imaging system ships with hardcoded default passwords - 'interfile' for the ftpclient user on the Interfile server and '2' for the LOCAL user on the Codonics printer's FTP server. An attacker with network access to these services can authenticate using these trivial credentials to gain unauthorized access.

MitigationImmediately change all default credentials on the affected system components. Contact GE Healthcare for proper authentication configuration and check for available firmware/software 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
Discovery VhApplication
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 system as GE Healthcare Discovery VH
    Review system documentation, device labeling, or network inventory to confirm the medical imaging system in use is the GE Healthcare Discovery VH model. Check the device's about/info screen or management interface for the product name and model number.
    Affected if The system is confirmed to be a GE Healthcare Discovery VH medical imaging device.
  2. Locate the Interfile server component
    Identify whether the Interfile server service is running on the system or connected network infrastructure. Check for open ports associated with Interfile or FTP services. Review system architecture documentation or network diagrams for Interfile server presence.
    Affected if An Interfile server component is present and accessible on the network.
  3. Attempt authentication to Interfile FTP with default credentials
    Using an FTP client, attempt to connect to the Interfile server using the username 'ftpclient' and password 'interfile'. Log the authentication result.
    Affected if Authentication succeeds with username 'ftpclient' and password 'interfile', indicating the default credential is still active.
  4. Locate the Codonics printer component
    Identify whether a Codonics printer is connected to the imaging system. Check network for Codonics device presence or review system configuration for printer connections.
    Affected if A Codonics printer with FTP server capability is present on the network.
  5. Attempt authentication to Codonics printer FTP with default credentials
    Using an FTP client, attempt to connect to the Codonics printer's FTP server using the username 'LOCAL' and password '2'. Log the authentication result.
    Affected if Authentication succeeds with username 'LOCAL' and password '2', indicating the default credential is still active.

The environment is affected if it contains a GE Healthcare Discovery VH system where either the Interfile server accepts 'ftpclient'/'interfile' credentials or the Codonics printer FTP accepts 'LOCAL'/'2' credentials.

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 default credentials on the affected system components. Contact GE Healthcare for proper authentication configuration and check for available firmware/software updates that may address this vulnerability.

Fix this in Discovery Vh Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2003-1603 — 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-2003-1603 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