dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-1630

HIGH · 7.7 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Path traversal vulnerability in “getAllFolderContents” function of Common Service Desktop, a GE HealthCare ultrasound device component

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

A path traversal vulnerability exists in the getAllFolderContents function of the Common Service Desktop component in GE HealthCare ultrasound devices. This flaw allows attackers to manipulate file path inputs to access files outside the intended directory boundaries, potentially exposing sensitive system files or configuration data.

MitigationApply vendor-provided security patches from GE HealthCare and implement network segmentation to restrict unauthorized access to the Common Service Desktop component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 GE HealthCare ultrasound device
    Confirm the device model by checking system information, device label, or running 'systeminfo' or 'hostname' commands if accessing the underlying OS. Cross-reference the model number against GE HealthCare ultrasound product documentation.
    Affected if The device is a GE HealthCare ultrasound system running the Common Service Desktop component.
  2. Check Common Service Desktop component presence
    Locate the Common Service Desktop executable or service on the device. Common paths may include C:\Program Files\GEHC\ or C:\GEHC\ directories. Use 'dir /s' or file explorer to search for 'CommonServiceDesktop' or 'CSD' named files.
    Affected if The Common Service Desktop component is installed on the ultrasound device.
  3. Verify getAllFolderContents function accessibility
    Examine the Common Service Desktop binary or its configuration files. Check if the getAllFolderContents function is exposed through API endpoints, web interfaces, or executable parameters. Review any accessible interfaces that accept file path inputs.
    Affected if The getAllFolderContents function is exposed and accepts user-controlled file path inputs.
  4. Test for path traversal vulnerability
    If interface access is available, attempt to access a known file outside the intended directory using '../' sequences in file path parameters (e.g., '../../windows/system32/config'). Observe if the system returns content from outside the expected directory.
    Affected if The application returns file contents when path traversal sequences are used in file path parameters.
  5. Review network exposure of Common Service Desktop
    Check network listening ports and firewall rules on the device. Identify if Common Service Desktop ports are accessible from network segments outside the medical device VLAN. Use 'netstat -an' to list listening ports.
    Affected if The Common Service Desktop component is accessible from network segments that are not restricted by network segmentation.

A user is affected if they operate a GE HealthCare ultrasound device with the Common Service Desktop component where the getAllFolderContents function accepts file path inputs and is accessible either locally or over the network without proper path traversal protection.

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

Apply vendor-provided security patches from GE HealthCare and implement network segmentation to restrict unauthorized access to the Common Service Desktop component.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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