CVE-2020-12048Phoenix Hemodialysis Delivery System SW 3.36 and 3.40, The Phoenix Hemodialysis device does not support data-in-transit encryption (e.g., TLS/SSL) when transmitting treatment and prescription data on…
Updated under an hour ago ()
Does this affect you?
It affects baxter phoenix_x36_firmware. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.45%, higher than 38% of scored CVEs.
Do this next
Free account, 1 product
Phoenix Hemodialysis Delivery System SW 3.36 and 3.40, The Phoenix Hemodialysis device does not support data-in-transit encryption (e.g., TLS/SSL) when transmitting treatment and prescription data on the network between the Phoenix system and the Exalis dialysis data management tool. An attacker with access to the network could observe sensitive treatment and prescription data sent between the Phoenix system and the Exalis tool.
- CVSS
- 7.5 HIGH (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weakness (CWE)
- CWE-319
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.45% (percentile 38)
- Assigned by
- icscert
- NVD analysis
- Modified
- Record last updated
- Aug 4, 2024
- First seen by InfoSec Signals
- Oct 12, 2026
Affected products
baxter phoenix_x36_firmware baxter:phoenix_x36_firmware | 3.36; 3.40 | NVD |
References
- https://www.us-cert.gov/ics/advisories/icsma-20-170-03x-refsource-misc, third-party-advisory, us-government-resource
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.