dbcve.org
Em2400 FirmwareOperating system · Baxter

CVE-2020-12008

HIGH · 7.5 CVSS v3.1 Published 2020-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Baxter ExactaMix EM 2400 Versions 1.10, 1.11 and ExactaMix EM1200 Versions 1.1, 1.2 systems use cleartext messages to communicate order information with an order entry system. This could allow an attacker with network access to view sensitive data including PHI.

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 confidence

The Baxter ExactaMix EM 2400 (v1.10, 1.11) and EM1200 (v1.1, 1.2) systems transmit order information to the order entry system using unencrypted cleartext messages, allowing network-adjacent attackers to intercept sensitive Protected Health Information (PHI) in transit.

MitigationImplement TLS/SSL encryption for all communications between ExactaMix systems and the order entry system, or establish a VPN/secure tunnel; alternatively, apply network segmentation to isolate these systems from untrusted networks.

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
Em2400 FirmwareOperating system
Affected:= 1.10= 1.11
Em1200 FirmwareOperating system
Affected:= 1.1= 1.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 ExactaMix device model and firmware version
    Access the device administration interface or system information screen on the Baxter ExactaMix EM2400 or EM1200 to retrieve the current firmware version. This is typically found in the system settings or maintenance section of the device console.
    Affected if The firmware version displayed is exactly 1.10 or 1.11 for EM2400, or exactly 1.1 or 1.2 for EM1200.
  2. Locate the order entry system integration settings
    Within the ExactaMix device administration panel, navigate to the network or communications configuration section where connections to the order entry system are defined. Look for settings related to data transmission or HL7/order messaging.
    Affected if The device is configured to send order information to an order entry system without TLS or SSL encryption explicitly enabled.
  3. Capture network traffic on the segment between ExactaMix and order entry system
    Use a network packet capture tool on the same network segment to observe data packets transmitted from the ExactaMix device to the order entry server. Examine the payload contents for cleartext patient data or order information.
    Affected if Captured packets show unencrypted, cleartext data containing order details or PHI traveling from the ExactaMix device to the order entry system.
  4. Verify encryption configuration for outbound communications
    In the device network settings, check whether there is a TLS, SSL, or encryption option enabled for the order transmission channel. Confirm if the connection protocol is set to a secure variant versus plaintext.
    Affected if Encryption is disabled or set to plaintext for communications with the order entry system, or no TLS/SSL option is available in the configuration.

You are affected if your ExactaMix EM2400 runs firmware 1.10 or 1.11 (or EM1200 runs 1.1 or 1.2) and the device transmits order data to the order entry system without encryption enabled, resulting in cleartext PHI on the network.

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

Implement TLS/SSL encryption for all communications between ExactaMix systems and the order entry system, or establish a VPN/secure tunnel; alternatively, apply network segmentation to isolate these systems from untrusted networks.

Fix this in Em2400 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12008 — 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-2020-12008 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