# CVE-2020-12012: Hardcoded credentials in Baxter ExactaMix EM 2400 & EM 1200

> An attacker with physical access can use hard-coded admin credentials to view or modify system configuration and sensitive data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2g9p-g9jc-w2xw

## What is CVE-2020-12012?

CVE-2020-12012 is a medium-severity vulnerability in Baxter ExactaMix EM 2400 & EM 1200, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Baxter 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2020-12012?

It affects 2 products.


Products: Baxter Em1200 Firmware, Baxter Em2400 Firmware.

## How do I fix CVE-2020-12012?

No fix has been published for CVE-2020-12012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-12012 being exploited?

There is no known exploitation of CVE-2020-12012 in the wild and no public exploit code.

## Other vulnerabilities in Baxter ExactaMix EM 2400 & EM 1200

- [CVE-2020-12016](https://insights.sbomify.com/CVE-2020-12016/): Hardcoded credentials in Baxter ExactaMix EM 2400 & EM 1200 (critical 9.8)
- [CVE-2020-12032](https://insights.sbomify.com/CVE-2020-12032/): Information disclosure in Baxter ExactaMix EM 2400 & EM 1200 (critical 9.1)
- [CVE-2020-12008](https://insights.sbomify.com/CVE-2020-12008/): Information disclosure in Baxter ExactaMix EM 2400 & EM 1200 (high 7.5)
- [CVE-2020-12020](https://insights.sbomify.com/CVE-2020-12020/): Privilege escalation in Baxter ExactaMix EM 2400 & EM 1200 (medium 6.1)
- [CVE-2020-12024](https://insights.sbomify.com/CVE-2020-12024/): Missing authorization in Baxter ExactaMix EM 2400 & EM 1200 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12012 and fix it if it is affected.

What it is: CVE-2020-12012 is a medium-severity vulnerability in Baxter ExactaMix EM 2400 & EM 1200, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12012 in the wild and no public exploit code.

Affected product: Baxter ExactaMix EM 2400 & EM 1200. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-12012/ (Markdown: https://insights.sbomify.com/CVE-2020-12012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-12012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-12012
- OSV: https://osv.dev/vulnerability/CVE-2020-12012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-12012/
Summaries are generated and may contain mistakes; the official description above is the record.