# CVE-2018-10622: Medtronic MyCareLink Patient Monitor Network Credential Weakness

> Attackers can recover stored network credentials from Medtronic MyCareLink monitors to bypass authentication and gain unauthorized access.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/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:** 10 Aug 2018
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-h42x-qcjr-3ww7

## What is CVE-2018-10622?

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

### Official description

Medtronic MyCareLink Patient Monitor uses per-product credentials that are stored in a recoverable format. An attacker can use these credentials for network authentication.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-313 (Cleartext Storage in a File or on Disk)

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

It affects 2 products.


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

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

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

## Is CVE-2018-10622 being exploited?

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

## Other vulnerabilities in Medtronic 24950 MyCareLink Monitor

- [CVE-2018-10626](https://insights.sbomify.com/CVE-2018-10626/): Medtronic MyCareLink 24950 Patient Monitor Insufficient Verification of Data Authenticity (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10622 is a medium-severity vulnerability in Medtronic 24950 MyCareLink Monitor, published on 10 Aug 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-10622 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-10622/ (Markdown: https://insights.sbomify.com/CVE-2018-10622/index.md)
```

## Sources

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

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