# CVE-2018-8849: Medtronic N'Vision Clinician Programmer Missing Encryption of Sensitive Data


- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 May 2018
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-w48q-g7g7-4m96

## What is CVE-2018-8849?

CVE-2018-8849 is a medium-severity vulnerability in Medtronic 8870 N’Vision removable Application Card, published on 18 May 2018. 

### Official description

Medtronic N'Vision Clinician Programmer 8840 N'Vision Clinician Programme and 8870 N'Vision removable Application Card do not encrypt PII and PHI while at rest.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 2 products.


Products: Medtronic N\'vision 8840 Firmware, Medtronic N\'vision 8870 Firmware.

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

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

## Is CVE-2018-8849 being exploited?

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

## Other vulnerabilities in Medtronic 8870 N’Vision removable Application Card

- [CVE-2018-10631](https://insights.sbomify.com/CVE-2018-10631/): Medtronic N'Vision Clinician Programmer Protection Mechanism Failure (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8849 is a medium-severity vulnerability in Medtronic 8870 N’Vision removable Application Card, published on 18 May 2018. 
Exploitation: There is no known exploitation of CVE-2018-8849 in the wild and no public exploit code.

Affected product: Medtronic 8870 N’Vision removable Application Card. 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-8849/ (Markdown: https://insights.sbomify.com/CVE-2018-8849/index.md)
```

## Sources

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

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