CVE-2019-25719: Dräger Infinity M540 VG4.1.1 Spoofing and DoS via Network Message Handling
Dräger Infinity Acute Care System and Standalone Infinity M540 patient monitors running software versions VG4.1.1, VG4.0.3, and lower contain network message handling vulnerabilities that allow network-adjacent attackers to spoof or tamper with data and cause denial-of-service conditions. Attackers with access to an enabled Infinity network port or physical proximity to a wireless access point can modify device settings such as alarm states or alarm limits, and overwhelm the system with incoming data causing the device to reboot and lose network functionality.
Security readout for executives and security teams
Plain-English summary
This vulnerability affects Dräger Infinity patient monitoring environments. An attacker on the same enabled network path, or near the relevant wireless access point, could tamper with monitor data/settings or cause monitor network disruption. The business concern is patient-safety impact from altered alarms, alarm limits, reboots, or loss of network functionality.
Executive priority
Treat as high priority for hospitals using affected Dräger monitoring systems. Prioritize inventory, vendor guidance review, and network containment because the described impacts involve alarm settings, device availability, and clinical monitoring reliability.
Technical view
CVE-2019-25719 is a network message handling issue in Dräger Infinity Acute Care System and Standalone Infinity M540 patient monitors running VG4.1.1, VG4.0.3, and lower. It is associated with CWE-924 and CVSS 4.0 score 8.8. The reported impact includes spoofing/tampering and denial of service from network-adjacent access.
Likely exposure
Exposure is most likely in clinical networks using affected Dräger Infinity Acute Care System or Standalone Infinity M540 monitors with enabled Infinity network ports or reachable wireless access points. Internet exposure is not indicated in the provided sources.
Exploitation context
The provided sources describe network-adjacent attack conditions without authentication or user interaction. They do not state active exploitation, and the CVE is not marked as CISA KEV in the provided bundle.
Researcher notes
Evidence in the bundle is sufficient for affected product family, attack adjacency, and impact types. It does not provide exploit proof, active exploitation, or a named patch level. Avoid assuming VG4.2 status without confirming vendor advisory details.
Mitigation direction
Review the Dräger advisory for supported fixes or configuration guidance.
Inventory affected Dräger monitors and software versions.
Restrict access to Infinity network ports to trusted clinical network segments.
Limit physical and wireless proximity access to relevant access points.
Monitor for unexpected reboots, network loss, or alarm setting changes.
Validation and detection
Identify all Infinity Acute Care System and Standalone Infinity M540 deployments.
Confirm software versions, especially VG4.1.1, VG4.0.3, and lower.
Verify Infinity network ports are not broadly reachable.
Review wireless coverage and access controls near clinical areas.
Check device and clinical logs for unexplained reboots or alarm changes.
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-924: 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-924 · source CWE mapping
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
Improper Enforcement of Message Integrity During Transmission in a Communication Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.