CVE-2020-6964
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 ApexPro Telemetry Server Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinical Information Center (CIC) Versions 4.X and 5.X, CARESCAPE Central Station (CSCS) Versions 1.X and CARESCAPE Central Station (CSCS) Versions 2.X, the integrated service for keyboard switching of the affected devices could allow attackers to obtain remote keyboard input access without authentication over the network.
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 exists in the keyboard switching service of GE Healthcare telemetry and clinical monitoring servers. An unauthenticated remote attacker can access the keyboard input functionality over the network, potentially capturing sensitive data entered by healthcare staff on affected systems.
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 data<= 4.2= 1.0= 2.0= 1.0= 2.0= 4.0= 5.0= 4.0= 5.0<= 4.2CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/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 GE Healthcare device modelLocate the device label or access the device management interface to confirm the exact model (Apexpro Telemetry Server, Carescape Central Station Mai700/Mas700, Clinical Information Center Mp100d/Mp100r, or Carescape Telemetry Server Mp100r)Affected if The device model matches any of the affected products listed in the CVE
-
Determine the installed firmware versionAccess the device system settings, about page, or maintenance interface to retrieve the firmware version numberAffected if The firmware version falls within the affected ranges: <= 4.2 for Apexpro Telemetry Server or Carescape Telemetry Server Mp100r; = 1.0 or = 2.0 for Carescape Central Station Mai700/Mas700; = 4.0 or = 5.0 for Clinical Information Center Mp100d/Mp100r
-
Verify keyboard switching service network accessibilityCheck if port 6000/tcp (typical keyboard service port) or the keyboard switching service port is listening and exposed to network access using netstat or port scanning tools from an external hostAffected if The keyboard switching service port is open and accessible from untrusted network segments
-
Confirm keyboard input functionality is enabledReview the device configuration or service status to verify the keyboard switching service daemon is running and enabledAffected if The keyboard switching service is active and operational on the device
The environment is affected if the device is one of the listed GE Healthcare models running an affected firmware version AND the keyboard switching service is network-accessible.
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 dataApply vendor-provided patches for affected versions; restrict network access to these critical medical devices using network segmentation and firewall controls to limit exposure to untrusted networks.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6964 — 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-2020-6964 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