CVE-2020-12012
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 & EM 1200, Versions ExactaMix EM2400 Versions 1.10, 1.11, 1.13, 1.14, ExactaMix EM1200 Versions 1.1, 1.2, 1.4, 1.5, Baxter ExactaMix EM 2400 Versions 1.10, 1.11, and 1.13, and ExactaMix EM1200 Versions 1.1, 1.2, and 1.4 have hard-coded administrative account credentials for the ExactaMix application. Successful exploitation of this vulnerability may allow an attacker with physical access to gain unauthorized access to view/update system configuration or data. 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 ExactaMix EM 2400 and EM 1200 infusion pump management systems contain hard-coded administrative credentials embedded in the application code. An attacker with physical access to the device can leverage these static credentials to authenticate as an administrator, gaining full access to view and modify system configuration, patient data, and operational settings, including potentially sensitive PHI.
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 labeling or system information that indicates whether the unit is an EM2400 or EM1200 infusion pump management systemAffected if The device is a Baxter ExactaMix EM2400 or EM1200 system
-
Check the installed firmware versionAccess the device system settings or firmware information screen to determine the current firmware versionAffected if The firmware version is 1.10, 1.11, 1.13, or 1.14 for EM2400, or 1.1, 1.2, 1.4, or 1.5 for EM1200
-
Verify physical access controlsInspect the physical location and access controls where the device is deployed to determine if unauthorized persons could gain physical accessAffected if The device is in an area with weak or no access controls allowing unauthorized physical proximity
-
Assess network exposure of the management interfaceReview network configuration to determine if the device administrative interface is accessible over the network rather than isolatedAffected if The device management interface is network-accessible beyond the local console
-
Check for credential change historyReview any available system logs or configuration records to determine if the administrative credentials have been changed from factory defaultsAffected if No credential rotation has been performed or the default hard-coded credentials remain in use
A user is affected if they have a Baxter ExactaMix EM2400 or EM1200 device running one of the listed firmware versions with the hard-coded administrative credentials still active and physical or network access available to an attacker.
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 dataContact Baxter for vendor-provided patches or firmware updates to replace hard-coded credentials. Implement physical access controls, restrict device network exposure, and monitor for unauthorized access. Consider network segmentation of medical devices and credential rotation if supported.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12012 — 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-12012 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