LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Certain Medtronic MyCareLink patient monitors contain a hard-coded operating system password. Someone must physically open the device and access its debug port to use it, but successful access could give privileged control over the device operating system.

Executive priority

Treat this as a moderate operational and patient-device security issue. It is not a remote internet-scale flaw, but unmanaged physical access could allow privileged device compromise. Prioritize inventory, physical controls, and vendor-guidance review.

Technical view

CVE-2018-8870 maps to CWE-259: use of a hard-coded password. The reported attack path requires physical access, case removal, debug-port connectivity, and use of the password to gain privileged OS access. CVSS 3.1 is 6.4 with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Medtronic 24950 MyCareLink Monitor and 24952 MyCareLink Monitor, listed as all versions in the source bundle. Risk is highest where devices are physically accessible to untrusted people.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation is constrained by physical access and high attack complexity, but successful compromise could affect the monitor’s operating system.

Researcher notes

The public facts provided are sufficient for scope and attack preconditions, but not for a specific patch statement. Avoid assuming a software update exists unless confirmed in Medtronic or ICS-CERT guidance.

Mitigation direction

  • Inventory 24950 and 24952 MyCareLink monitors in clinical and patient environments.
  • Review Medtronic and ICS-CERT guidance for supported mitigations or replacement direction.
  • Restrict physical access to monitors and storage areas.
  • Add tamper-evident handling and chain-of-custody controls where practical.
  • Remove unused affected monitors from accessible locations.

Validation and detection

  • Confirm whether deployed monitors are model 24950 or 24952.
  • Check procurement and biomedical engineering records for affected inventory.
  • Review physical access controls for rooms, storage, and patient areas.
  • Confirm whether vendor guidance has been reviewed and documented.
  • Look for signs of device case tampering during maintenance checks.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-259: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-8870 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H0.55.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2018-8870Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Medtronic24950 MyCareLink MonitorAll versionsunaffected
Medtronic24952 MyCareLink MonitorAll versionsunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-259 · source CWE mapping

Use of Hard-coded Password

Use of Hard-coded Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.