CVE-2019-25724
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 · uneditedDräger Infinity M300 patient worn monitors with software version VG2.x and earlier contain a network-based denial of service vulnerability that allows attackers with access to the hospital or Infinity Network to repeatedly trigger device reboots until the device enters a fail state requiring manual restart. Attackers can exploit this vulnerability to cause loss of wireless network connectivity, temporary loss of patient monitoring, and interruption of alarm functionality until the device is manually recovered.
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 confidenceThe Dräger Infinity M300 patient monitor contains a network-based denial of service vulnerability where attackers with access to the hospital or Infinity Network can repeatedly trigger device reboots, eventually causing the device to enter a fail state that requires manual restart. This leads to loss of wireless connectivity, interruption of patient monitoring, and loss of alarm functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device modelLocate the physical device or network inventory to confirm it is a Dräger Infinity M300 patient monitor. Check device labels, documentation, or network scanning results for the exact model identifier.Affected if The device is an Infinity M300 monitor and is present on your network.
-
Determine the software versionAccess the device's system information menu or management interface to identify the installed VG version number. Compare this version to the affected range of VG2.x and earlier.Affected if The installed VG version is VG2.x or any version prior to VG2 (e.g., VG1.x).
-
Verify network accessibilityCheck network configuration settings on the device or corresponding network infrastructure to determine if the device has an IP address and is reachable on the hospital or Infinity Network.Affected if The device is connected to a network without isolation from untrusted or unauthorized network segments.
-
Inspect network segmentationReview network infrastructure configuration (VLANs, firewalls, access control lists) to determine if the device is isolated from non-medical or untrusted network segments.Affected if The device shares a network segment with general hospital systems or is accessible from networks outside the intended Infinity Network.
-
Check for reboot patternsReview device event logs, network monitoring logs, or system uptime records for evidence of repeated or unexplained reboots occurring in short succession.Affected if Logs show frequent unexpected reboots or device fail states requiring manual restart.
A user is affected if they have a Dräger Infinity M300 monitor running software version VG2.x or earlier that is accessible on a network segment without proper isolation from untrusted access.
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 dataImplement network segmentation to isolate medical devices from untrusted networks and apply strict access controls to prevent unauthorized network access to the Infinity Network. Monitor for abnormal reboot patterns and consider firmware updates if available from Dräger.
- Consultation8.0 h
- Implementation16.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 $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25724 — 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-2019-25724 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