CVE-2020-6977
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 · uneditedA restricted desktop environment escape vulnerability exists in the Kiosk Mode functionality of affected devices. Specially crafted inputs can allow the user to escape the restricted environment, resulting in access to the underlying operating system. Affected devices include the following GE Ultrasound Products: Vivid products - all versions; LOGIQ - all versions not including LOGIQ 100 Pro; Voluson - all versions; Versana Essential - all versions; Invenia ABUS Scan station - all versions; Venue - all versions not including Venue 40 R1-3 and Venue 50 R4-5
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 restricted desktop environment escape vulnerability exists in the Kiosk Mode functionality of GE Ultrasound devices. Specially crafted inputs allow users to break out of the restricted Kiosk environment and gain access to the underlying operating system. This affects multiple product lines including Vivid, LOGIQ, Voluson, Versana Essential, Invenia ABUS Scan station, and Venue 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 dataall versionsall versionsall versionsall versionsall 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/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 the GE Ultrasound device modelAccess the device system information or startup screen to determine the exact model (e.g., Vivid E95, Vivid E90, LOGIQ E9, etc.)Affected if The device model matches any of the following: Vivid E95, Vivid E90, Vivid S70n, Vivid T8, Vivid T9, Vivid Iq, LOGIQ E10, LOGIQ E9, Voluson, Versana Essential, Invenia ABUS Scan station, or Venue systems
-
Check the installed firmware versionAccess the device firmware/version information through the system settings or maintenance menu. Note that all listed versions are affected.Affected if Any firmware version is installed on an affected device model, since the advisory states all versions are affected
-
Determine if Kiosk Mode is enabledAccess the device configuration or administrative settings to verify whether the Kiosk Mode restriction feature is currently active or configuredAffected if Kiosk Mode is enabled or configured on the device, as this is the specific feature with the vulnerability
-
Inspect for unexpected system access or modificationsReview system logs, file system changes, or unusual processes that may indicate a Kiosk Mode bypass has occurredAffected if Evidence of unauthorized access to the underlying operating system, unexpected applications, or modified system settings that were not authorized by administrators
A user is affected if they operate any of the listed GE Ultrasound device models with Kiosk Mode enabled, since all firmware versions for these models contain the vulnerability.
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 dataContact GE Healthcare for official patches or firmware updates addressing this vulnerability. If patches are unavailable, consider disabling Kiosk Mode functionality or implementing additional physical and logical access controls to limit exposure.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6977 — 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-6977 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