Dräger Infinity Acute Care System and Standalone Infinity M540 patient monitors versions VG4.1.1, VG4.0.3, and lower (with VG4.2 partially affected) contain a network message handling vulnerability that allows remote attackers to inject spoofed or tampered data and cause denial-of-service conditions. Attackers can compromise network communications to modify device settings such as alarm states or alarm limits, or overwhelm the system with excessive network traffic causing the Cockpit or M540 to reboot and lose network functionality.
Security readout for executives and security teams
Plain-English summary
This vulnerability affects Dräger Infinity patient monitoring systems and can let a remote, unauthenticated attacker disrupt monitoring or alter network-delivered settings. In clinical environments, the business concern is patient safety disruption, alarm reliability, and operational downtime rather than data theft.
Executive priority
Treat this as high priority where affected monitors support active care areas. The key urgency is reducing preventable disruption to patient monitoring while coordinating any changes through clinical operations and vendor support.
Technical view
CVE-2022-4992 is a CWE-345 improper verification issue in network message handling. Spoofed or tampered network messages may modify settings such as alarm states or limits, while excessive traffic can cause Cockpit or M540 reboot and loss of network functionality.
Likely exposure
Exposure is most relevant to healthcare environments running Dräger Infinity Acute Care System or Standalone Infinity M540 patient monitors on VG4.1.1, VG4.0.3, lower versions, or partially affected VG4.2 deployments.
Exploitation context
The provided sources do not state active exploitation, and this CVE is not marked KEV. Risk still matters because attack requirements are low: network access, no privileges, and no user interaction.
Researcher notes
The source bundle identifies impact and affected version families but does not provide exploit evidence or a complete fix matrix. Validate against the vendor advisory before declaring remediation complete.
Mitigation direction
Review Dräger PSA-19-255-03 and current Dräger guidance for approved remediation.
Confirm affected software versions with biomedical engineering or the device owner.
Prioritize vendor-approved updates or compensating controls for exposed clinical networks.
Limit unnecessary network reachability to affected monitoring systems under existing clinical policy.
Validation and detection
Inventory Dräger Infinity Acute Care System and Standalone Infinity M540 deployments.
Identify devices running VG4.1.1, VG4.0.3, lower versions, or VG4.2.
Check whether affected devices are reachable from non-clinical or unmanaged networks.
Review operational records for unexpected reboots, lost network functionality, or alarm-setting anomalies.
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-345: 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-345 · source CWE mapping
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.