CVE-2019-10966
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 · uneditedIn 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.
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 confidenceThis vulnerability affects GE Aestiva and Aespire anesthesia machines (versions 7100, 7900). Serial medical devices connected through an unsecured terminal server to TCP/IP networks can be remotely exploited, allowing attackers to modify device configuration and silence clinical alarms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 the anesthesia machine modelInspect the physical device label or access the device's system information menu to confirm the exact model number (Aestiva 7100, Aestiva 7900, Aespire 7100, or Aespire 7900)Affected if The model is GE Aestiva 7100, Aestiva 7900, Aespire 7100, or Aespire 7900
-
Verify the firmware versionAccess the device's maintenance or settings menu and locate the firmware version information screenAffected if Any firmware version is installed (all versions are affected)
-
Determine if the device is network-connected via terminal serverReview network documentation, check the device's network configuration settings, or inspect the physical cabling to identify if serial ports are connected through a terminal server to TCP/IP networksAffected if The device is connected to IP networks through a terminal server (serial-to-Ethernet bridge)
-
Assess terminal server security configurationAccess the terminal server management interface and verify whether encryption (such as SSH, SSL/TLS) and authentication are enabled for remote accessAffected if The terminal server lacks encrypted protocols and strong authentication, allowing unauthenticated network access
You are affected if you operate any GE Aestiva or Aespire 7100/7900 anesthesia machine connected to a network via an unsecured terminal server, as this enables remote attackers to modify device configuration and silence alarms.
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 medical devices on a dedicated, secured network segment; replace or properly secure the terminal server with encrypted authentication; implement network access controls to prevent unauthorized modifications to device configuration.
- Consultation12.0 h
- Implementation24.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 $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10966 — 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-2019-10966 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