CVE-2024-1629
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 · uneditedPath traversal vulnerability in “deleteFiles” 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 confidenceA path traversal vulnerability exists in the deleteFiles function of GE HealthCare's Common Service Desktop, a component of ultrasound devices. This allows attackers to manipulate file paths using '..' sequences to delete arbitrary files on the system beyond the intended directory.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GE HealthCare Common Service Desktop installationSearch for the Common Service Desktop software on the system - look for executables, services, or installed applications named 'Common Service Desktop' or similar GE HealthCare ultrasound-related componentsAffected if The software is present on the system
-
Determine the installed versionLocate version information in the software's installation directory, registry entries, or application metadata. Check for version files, About dialogs, or product information in the GE HealthCare ultrasound device management interfaceAffected if The installed version falls within any affected version range (if known) or cannot be determined to be patched
-
Verify deleteFiles function accessibilityExamine the application's exposed APIs, web services, or interfaces for the deleteFiles endpoint. Check network service configurations and access controls on ultrasound device management interfacesAffected if The deleteFiles function is exposed and accessible (particularly over network) without proper authentication or validation controls
-
Check for path traversal protectionReview any available logs or configuration for the Common Service Desktop to see if input validation is implemented on file deletion operationsAffected if No path traversal protections (input validation) are visible in the file deletion functionality
You are affected if GE HealthCare Common Service Desktop is installed and the deleteFiles function is exposed without path traversal input validation protections in place.
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 dataImplement strict input validation on the deleteFiles function to sanitize file path inputs, restricting access to only permitted directories and rejecting path traversal sequences.
- Consultation8.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1629 — 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-2024-1629 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