CVE-2020-10598
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 BD Pyxis MedStation ES System v1.6.1 and Pyxis Anesthesia (PAS) ES System v1.6.1, a restricted desktop environment escape vulnerability exists in the kiosk mode functionality of affected devices. Specially crafted inputs could allow the user to escape the restricted environment, resulting in access to sensitive data.
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 in BD Pyxis MedStation ES and Pyxis Anesthesia (PAS) ES v1.6.1 allows a user to escape the restricted kiosk mode environment through specially crafted inputs, potentially exposing sensitive patient data and medication information managed by these clinical 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= 1.6.1= 1.6.1CVSS 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
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/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 exact BD Pyxis product modelLocate the physical device or system inventory and confirm whether it is a BD Pyxis MedStation ES or BD Pyxis Anesthesia Station (PAS) ES system. Check device labels, management console, or asset inventory records.Affected if The device is neither a Pyxis MedStation ES nor a Pyxis Anesthesia PAS ES system.
-
Check the installed firmware versionAccess the device admin interface, system diagnostics menu, or firmware management console to retrieve the current firmware version. Compare against version 1.6.1.Affected if The firmware version is exactly 1.6.1 for either product.
-
Verify if kiosk mode is enabledCheck the device configuration settings to determine whether the restricted kiosk mode environment is currently active. Look for kiosk or lockdown settings in the system administration panel.Affected if Kiosk mode is enabled and the firmware is version 1.6.1.
-
Confirm the system is a clinical production environmentVerify that the device is deployed in an active clinical setting handling patient data and medication management, not in a lab or isolated test environment.Affected if The affected firmware version 1.6.1 is running in a production clinical environment with kiosk mode enabled.
A user is affected if their BD Pyxis MedStation ES or Pyxis Anesthesia Station ES system is running firmware version 1.6.1 with kiosk mode enabled, allowing specially crafted inputs to escape the restricted environment and potentially expose patient data.
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-supplied patches from BD (Becton, Dickinson and Company) when available; until then, implement compensating controls such as strict physical access controls, network segmentation of medical devices, and enhanced monitoring for anomalous kiosk escape attempts.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10598 — 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-10598 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