CVE-2020-12024
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 · uneditedBaxter ExactaMix EM 2400 versions 1.10, 1.11, 1.13, 1.14 and ExactaMix EM1200 Versions 1.1, 1.2, 1.4 and 1.5 does not restrict access to the USB interface from an unauthorized user with physical access. Successful exploitation of this vulnerability may allow an attacker with physical access to the system the ability to load an unauthorized payload or unauthorized access to the hard drive by booting a live USB OS. This could impact confidentiality and integrity of the system and risk exposure of sensitive information 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 confidenceThe Baxter ExactaMix EM 2400 and EM1200 intravenous compounding systems do not restrict access to the USB interface, allowing any user with physical access to boot from a live USB operating system or load unauthorized payloads. This exposes the hard drive contents and enables modification of the system's software, compromising confidentiality and integrity of Protected Health Information (PHI) and other sensitive data.
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= 1.10= 1.11= 1.13= 1.14= 1.1= 1.2= 1.4= 1.5CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the ExactaMix device modelLocate the device nameplate or system information screen on the Baxter ExactaMix system. Confirm it is an EM2400 or EM1200 intravenous compounding system.Affected if The device is an EM2400 or EM1200 model - this is required for the vulnerability to apply.
-
Check the installed firmware versionAccess the system's firmware/settings menu or check the device documentation label. Look for a firmware version number such as 1.10, 1.11, 1.13, 1.14 for EM2400 or 1.1, 1.2, 1.4, 1.5 for EM1200.Affected if The firmware version matches exactly 1.10, 1.11, 1.13, or 1.14 on EM2400, or 1.1, 1.2, 1.4, or 1.5 on EM1200.
-
Verify USB boot is disabled in BIOSReboot the device and enter the BIOS/UEFI setup (typically by pressing Del, F2, or F12 during boot). Navigate to the Boot order settings and confirm whether USB devices are listed as a boot option or enabled for booting.Affected if USB boot is enabled or USB devices appear in the boot order - the device is vulnerable to booting from an unauthorized live USB.
-
Confirm BIOS password protection is enabledIn the BIOS/UEFI setup, check the security settings for a BIOS or supervisor password. Verify that password protection is required to access or modify BIOS settings.Affected if No BIOS password is set, or BIOS settings can be modified without authentication.
If the device is an EM2400 or EM1200 with firmware version 1.10/1.11/1.13/1.14 or 1.1/1.2/1.4/1.5 respectively, and USB boot is enabled or BIOS lacks password protection, the device is affected by this vulnerability.
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 dataImplement physical access controls (locked enclosures, restricted facility access) and configure BIOS to disable USB boot, enable BIOS passwords, and consider USB port disablement if supported by the device firmware or through vendor-provided updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12024 — 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-2020-12024 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