# CVE-2024-27110: Elevation of privilege vulnerability in GE HealthCare EchoPAC products

> Attackers can elevate privileges in GE HealthCare EchoPAC products, potentially gaining unauthorized control over the medical imaging system.

- **Severity:** High 8.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3xj2-xvqh-gvp5

## What is CVE-2024-27110?

CVE-2024-27110 is a high-severity vulnerability in GE HealthCare EchoPAC Software Only, published on 14 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Elevation of privilege vulnerability in GE HealthCare EchoPAC products

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2024-27110?


## How do I fix CVE-2024-27110?

No fix has been published for CVE-2024-27110 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-27110 being exploited?

There is no known exploitation of CVE-2024-27110 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27110 and fix it if it is affected.

What it is: CVE-2024-27110 is a high-severity vulnerability in GE HealthCare EchoPAC Software Only, published on 14 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27110 in the wild and no public exploit code.

Affected product: GE HealthCare EchoPAC Software Only. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-27110/ (Markdown: https://insights.sbomify.com/CVE-2024-27110/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27110
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27110
- OSV: https://osv.dev/vulnerability/CVE-2024-27110

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-27110/
Summaries are generated and may contain mistakes; the official description above is the record.