CVE-2024-1628
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 · uneditedOS command injection vulnerabilities in GE HealthCare ultrasound devices
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 confidenceOS command injection vulnerabilities in GE HealthCare ultrasound devices allow attackers to execute arbitrary operating system commands by injecting malicious input into vulnerable parameters. This could enable full compromise of the device, potentially affecting patient data integrity and system availability.
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
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the device modelCheck the device label, startup screen, or system information menu for GE HealthCare ultrasound device branding and model numberAffected if The device is a GE HealthCare ultrasound system (e.g., LOGIQ, Voluson, Vivid series)
-
Verify network exposure of management interfacesCheck if the device management port (typically HTTP/HTTPS on the device IP) is accessible from untrusted network segments or directly from the internet by reviewing network firewall rules and VLAN configurationAffected if Management or service ports are exposed to networks outside the isolated ultrasound segment
-
Assess remote access featuresReview device configuration for enabled remote access features such as remote desktop, telnet, SSH, or vendor remote support tools that accept external inputAffected if Remote access services or web-based management interfaces are enabled and accessible
-
Check for default or weak credentialsAttempt to identify if default credentials are in use for device web interfaces or service accounts by reviewing documentation or testing against known GE default credential patternsAffected if Default vendor credentials have not been changed on administrative interfaces
-
Inspect input handling in clinical softwareReview any connected PACS, DICOM workstations, or clinical software that forwards data to the ultrasound device for lack of input sanitization in device-facing parametersAffected if Third-party software forwards unsanitized user input to device management functions
You are affected if you operate a GE HealthCare ultrasound device with exposed or accessible management interfaces that accept external input without proper validation.
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 dataIsolate ultrasound devices on restricted network segments, apply vendor-provided patches when available, and implement input validation and least-privilege controls on affected systems.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1628 — 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-1628 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