Security readout for executives and security teams
These Medtronic programmer systems may store patient or personal health information without adequate encryption. If someone gets physical access to a device or its storage, they may be able to read sensitive data. The main business risk is patient privacy exposure, not service disruption. Exposure is likely limited to healthcare, clinical engineering, or servicing environments that possess the listed Medtronic programmer devices. Risk depends on whether PHI or PII is stored locally and whether unauthorized physical access, loss, resale, repair, or disposal is plausible. Treat as a moderate privacy and compliance issue for environments with the affected devices. It should be prioritized in asset governance and physical security programs, but it is not presented as an active remote compromise threat in the supplied sources. Mitigation focus: Check Medtronic and ICS-CERT advisories for official mitigation or update guidance.; Restrict physical access to affected programmer devices and storage media.; Handle the devices as systems that may contain PHI or PII..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-311: 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 lookupCVE-2018-18984 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N0.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.6MediumVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- 106215CVE reference
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-347-01CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.