# CVE-2019-10966: Auth bypass in Aestiva and Aespire

> An attacker can remotely modify configuration and silence alarms on GE anesthesia machines if an unsecured terminal server is added to the network.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6rp2-2q6m-xv22

## What is CVE-2019-10966?

CVE-2019-10966 is a medium-severity authentication bypass vulnerability in GE Aestiva and Aespire, published on 10 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In GE Aestiva and Aespire versions 7100 and 7900, a vulnerability exists where serial devices are connected via an added unsecured terminal server to a TCP/IP network configuration, which could allow an attacker to remotely modify device configuration and silence alarms.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-10966?

It affects 4 products.


Products: Ge Aespire 7100 Firmware, Ge Aespire 7900 Firmware, Ge Aestiva 7100 Firmware, Ge Aestiva 7900 Firmware.

## How do I fix CVE-2019-10966?

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

## Is CVE-2019-10966 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10966 and fix it if it is affected.

What it is: CVE-2019-10966 is a medium-severity authentication bypass vulnerability in GE Aestiva and Aespire, published on 10 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10966 in the wild and no public exploit code.

Affected product: GE Aestiva and Aespire. 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-2019-10966/ (Markdown: https://insights.sbomify.com/CVE-2019-10966/index.md)
```

## Sources

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

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