# CVE-2018-8870: Medtronic MyCareLink Patient Monitor Use of Hard-coded Password

> An attacker with physical access can use a hard-coded password to gain privileged operating system access on Medtronic MyCareLink monitors.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Jul 2018
- **Updated:** 22 May 2025
- **Also known as:** GHSA-7jf7-367c-mvv4

## What is CVE-2018-8870?

CVE-2018-8870 is a medium-severity vulnerability in Medtronic 24950 MyCareLink Monitor, published on 2 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Medtronic 24950 MyCareLink Monitor and 24952 MyCareLink Monitor contains a hard-coded operating system password. An attacker with physical access can remove the case of the device, connect to the debug port, and use the password to gain privileged access to the operating system.

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

## Which versions are affected by CVE-2018-8870?

It affects 2 products.


Products: Medtronic 24950 Mycarelink Monitor Firmware, Medtronic 24952 Mycarelink Monitor Firmware.

## How do I fix CVE-2018-8870?

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

## Is CVE-2018-8870 being exploited?

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

## Other vulnerabilities in Medtronic 24950 MyCareLink Monitor

- [CVE-2018-8868](https://insights.sbomify.com/CVE-2018-8868/): Medtronic MyCareLink Patient Monitor Exposed Dangerous Method or Function (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8870 and fix it if it is affected.

What it is: CVE-2018-8870 is a medium-severity vulnerability in Medtronic 24950 MyCareLink Monitor, published on 2 Jul 2018. 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-2018-8870 in the wild and no public exploit code.

Affected product: Medtronic 24950 MyCareLink Monitor. 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-2018-8870/ (Markdown: https://insights.sbomify.com/CVE-2018-8870/index.md)
```

## Sources

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

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