CVE-2019-13530
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 · uneditedPhilips 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). An attacker can use these credentials to login via ftp and upload a malicious firmware.
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 · high confidenceHardcoded/default credentials exist in Philips IntelliVue WLAN patient monitors (firmware A.03.09 and A.01.09). These credentials allow unauthorized FTP authentication, enabling attackers to upload malicious firmware to the affected medical devices.
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= a.03.09= a.03.09= a01.09= a.01.09CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the IntelliVue monitor model and firmware versionAccess the device's system information menu via the front panel or check via SNMP/network discovery. For CLI access, log in and run 'show version' or equivalent command.Affected if The device is an MP20, MP90, MP5, 5SC, MP2, X2, MX800, MX700, or MX600 running firmware A.03.09 or A.01.09 (exact version match)
-
Determine if FTP service is enabled on the deviceScan the device IP address for open FTP port (port 21) using nmap or similar network scanner: 'nmap -p 21 <device_ip>'Affected if FTP port 21 is open and accepting connections
-
Check FTP authentication with default credentialsAttempt FTP login to the device using the documented default credentials for the affected firmware versionsAffected if Default or hardcoded credentials successfully authenticate to FTP
-
Verify FTP service exposure to networkReview network segmentation and firewall rules to determine if the device FTP port is accessible from untrusted network segmentsAffected if FTP service is reachable from outside the protected medical device network segment
The environment is affected if Philips IntelliVue WLAN monitors are running the specific firmware versions A.03.09 or A.01.09 AND FTP service is enabled and accessible with default credentials.
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 dataChange default credentials immediately, apply vendor firmware updates if available, disable unused FTP services, and implement network segmentation to limit exposure of medical devices.
- Consultation8.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,976.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13530 — 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-13530 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