dbcve.org
Intellivue Mp Monitors Mp20 Mp90 FirmwareOperating system · Philips

CVE-2019-13534

HIGH · 7.2 CVSS v3.1 Published 2019-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Philips IntelliVue WLAN, portable patient monitors, WLAN Version A, Firmware A.03.09, WLAN Version A, Firmware A.03.09, Part #: M8096-67501, WLAN Version B, Firmware A.01.09, Part #: N/A (Replaced by Version C) and WLAN Version B, Firmware A.01.09, Part #: N/A (Replaced by Version C). The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.

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 confidence

The Philips IntelliVue WLAN patient monitors download and execute code from remote locations without verifying the origin or integrity of that code, allowing unauthenticated remote attackers to inject and execute arbitrary malicious code on the affected devices.

MitigationUpdate affected devices to vendor-provided patched firmware versions and implement network segmentation to limit exposure to untrusted networks. If patching is not immediately possible, monitor network traffic for suspicious download activity and restrict the device's network connectivity.

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
Intellivue Mp Monitors Mp20 Mp90 FirmwareOperating system
Affected:= a.03.09
Intellivue Mp Monitors Mp5\/5sc FirmwareOperating system
Affected:= a.03.09
Intellivue Mp Monitors Mp2\/x2 FirmwareOperating system
Affected:= a01.09
Intellivue Mp Monitors Mx800\/700\/600 FirmwareOperating system
Affected:= a.01.09

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IntelliVue WLAN monitors on your network
    Scan your network for Philips IntelliVue MP20, MP90, MP5, MP5SC, MP2, X2, MX800, MX700, or MX600 patient monitors. Check device inventory or use network discovery tools to locate these specific model numbers.
    Affected if Any of these Philips IntelliVue monitor models are present on your network
  2. Check firmware version on IntelliVue monitors
    Access the monitor's system information or maintenance menu to retrieve the installed firmware version. Compare against affected versions: a.03.09 (MP20/MP90, MP5/5SC) or a01.09 (MP2/X2, MX800/700/600).
    Affected if The monitor displays firmware version a.03.09 or a01.09 exactly as shown in the affected products list
  3. Verify WLAN connectivity is enabled
    On the monitor, navigate to the network settings or WLAN configuration menu. Check if the wireless network interface is turned on and actively connected to a network.
    Affected if WLAN is enabled and the monitor has an active wireless connection - this is the attack vector for remote code injection
  4. Inspect network exposure of the device
    Review network firewall rules, VLAN placement, and access control lists to determine if the monitor's WLAN interface can reach untrusted or external IP addresses, particularly remote locations not under your organization's control.
    Affected if The monitor's WLAN interface can initiate outbound connections to untrusted or remote networks without inspection or restriction

Your environment is affected if you have any Philips IntelliVue MP20, MP90, MP5, MP5SC, MP2, X2, MX800, MX700, or MX600 monitors running firmware version a.03.09 or a01.09 with WLAN enabled and exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected devices to vendor-provided patched firmware versions and implement network segmentation to limit exposure to untrusted networks. If patching is not immediately possible, monitor network traffic for suspicious download activity and restrict the device's network connectivity.

Fix this in Intellivue Mp Monitors Mp20 Mp90 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-13534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-13534 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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