# CVE-2017-12725: Hardcoded credentials in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump

> Hard-coded credentials in the Medfusion 4000 pump allow attackers to bypass authentication and access network communications.

- **Severity:** Medium 5.6 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-chgj-p4c2-8wqj

## What is CVE-2017-12725?

CVE-2017-12725 is a medium-severity vulnerability in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use of Hard-coded Credentials issue was discovered in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump, Version 1.1, 1.5, and 1.6. The pump with default network configuration uses hard-coded credentials to automatically establish a wireless network connection. The pump will establish a wireless network connection even if the pump is Ethernet connected and active; however, if the wireless association is established and the Ethernet cable is attached, the pump does not attach the network stack to the wireless network. In this scenario, all network traffic is instead directed over the wired Ethernet connection.

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

## Which versions are affected by CVE-2017-12725?

It affects 1 product.


Products: Smiths-Medical Medfusion 4000 Wireless Syringe Infusion Pump.

## How do I fix CVE-2017-12725?

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

## Is CVE-2017-12725 being exploited?

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

## Other vulnerabilities in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump

- [CVE-2017-12718](https://insights.sbomify.com/CVE-2017-12718/): Memory corruption in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump (high 8.1)
- [CVE-2017-12720](https://insights.sbomify.com/CVE-2017-12720/): Missing authorization in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump (high 8.1)
- [CVE-2017-12724](https://insights.sbomify.com/CVE-2017-12724/): Hardcoded credentials in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump (high 8.1)
- [CVE-2017-12726](https://insights.sbomify.com/CVE-2017-12726/): Hardcoded credentials in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump (high 7.3)
- [CVE-2017-12721](https://insights.sbomify.com/CVE-2017-12721/): Weak cryptography in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12725 and fix it if it is affected.

What it is: CVE-2017-12725 is a medium-severity vulnerability in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12725 in the wild and no public exploit code.

Affected product: Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump. 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-2017-12725/ (Markdown: https://insights.sbomify.com/CVE-2017-12725/index.md)
```

## Sources

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

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