CVE-2024-1486
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 · uneditedElevation of privileges via misconfigured access control list 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 confidenceA misconfigured access control list (ACL) on GE HealthCare ultrasound devices allows an authenticated attacker to elevate privileges beyond their assigned role, potentially gaining administrative or unauthorized access to sensitive device functions and patient data.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 GE HealthCare ultrasound deviceLocate the device model number and firmware version from the device system information menu or startup logs. Confirm it is a GE HealthCare ultrasound system.Affected if Device is a GE HealthCare ultrasound system and ACL configuration exists on the device.
-
Locate ACL configuration fileAccess the device service or administrative interface. Navigate to the security or access control settings panel. Identify and retrieve the ACL configuration file or view the access control list entries.Affected if ACL configuration file is present and accessible through the device interface.
-
Examine role definitions and assigned privilegesReview all defined user roles (e.g., administrator, clinician, technician) and their associated permission sets. Check which roles are permitted access to sensitive functions like patient data management, device configuration, or system administration.Affected if Multiple user roles exist and some roles have permissions beyond what is required for their intended function.
-
Verify privilege boundary enforcementTest or inspect whether a user assigned a lower-privilege role can access functions designated for higher-privilege roles. Check ACL rules for any permissions that allow cross-role access to administrative or sensitive functions.Affected if A role with limited privileges can access functions or data assigned to a higher-privilege role, indicating ACL misconfiguration.
-
Check for overly permissive ACL entriesReview ACL entries for any rules that grant broad or wildcard permissions. Look for entries that allow ALL or elevated access to sensitive device functions or patient data repositories.Affected if ACL contains entries granting unrestricted or excessive access to sensitive functions beyond what the role should require.
A user is affected if they operate a GE HealthCare ultrasound device where the ACL configuration allows authenticated users to access functions beyond their assigned role privileges.
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 dataReview and remediate ACL configurations on affected ultrasound devices according to GE HealthCare guidance; verify that least-privilege principles are enforced for all user roles.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1486 — 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-1486 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