CVE-2019-25723: Dräger Perseus A500 2.00-2.02 DoS via Medibus Interface
Dräger Perseus A500 software versions 2.00 through 2.02 contains an improper input handling vulnerability that allows external attackers to cause a denial of service by sending specifically crafted non-Medibus-compliant data through the Medibus interface. Attackers can overload the internal processor with malformed data to trigger a warm restart, causing ventilation pressure to drop to ambient level and interrupting ventilation for several seconds before therapy resumes.
Security readout for executives and security teams
Plain-English summary
This flaw can make a Dräger Perseus A500 anesthesia workstation restart when malformed data reaches its Medibus interface. During the restart, ventilation pressure can drop to ambient level and ventilation can pause for several seconds before therapy resumes. The business concern is patient-care disruption, not data theft.
Executive priority
Prioritize clinical inventory and exposure reduction in operating-room or anesthesia environments. This is not reported as actively exploited, but the patient-care consequence makes validation important.
Technical view
CVE-2019-25723 is improper input handling in Dräger Perseus A500 software 2.00 through 2.02, with source data also listing 2.03. Crafted non-Medibus-compliant data sent through the Medibus interface can overload the internal processor and trigger a warm restart, causing temporary ventilation interruption. CVSS v4.0 score is 6.3.
Likely exposure
Exposure is most likely in clinical environments running affected Perseus A500 systems where the Medibus interface is connected and reachable by untrusted or insufficiently controlled devices or networks.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The issue is remotely reachable per the CVSS vector, but attack complexity is high and impact is availability-focused.
Researcher notes
There is a version inconsistency in the supplied bundle: the description says 2.00 through 2.02, while the affected list includes 2.03. Treat 2.03 as needing vendor confirmation before excluding it.
Mitigation direction
Review the Dräger advisory for supported remediation guidance.
Confirm affected software versions with biomedical engineering or Dräger support.
Restrict untrusted access to the Medibus interface.
Segment clinical device networks from general-purpose networks.
Monitor for unexpected warm restarts or ventilation interruptions.
Validation and detection
Inventory Perseus A500 devices and installed software versions.
Identify whether the Medibus interface is enabled and connected.
Map systems or networks that can reach the Medibus interface.
Check device logs or clinical reports for unexplained warm restarts.
Verify remediation status against Dräger guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1286: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1286 · source CWE mapping
Improper Validation of Syntactic Correctness of Input
Improper Validation of Syntactic Correctness of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.