# CVE-2017-14012: Weak cryptography in ZOOM LATITUDE PRM

> An attacker with physical access can read unencrypted Protected Health Information stored on the Boston Scientific ZOOM LATITUDE PRM device.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 1 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hp6q-87rc-fwjw

## What is CVE-2017-14012?

CVE-2017-14012 is a medium-severity vulnerability in Boston Scientific ZOOM LATITUDE PRM, published on 1 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Boston Scientific ZOOM LATITUDE PRM Model 3120 does not encrypt PHI at rest. CVSS v3 base score: 4.6; CVSS vector string: AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

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

## Which versions are affected by CVE-2017-14012?

It affects 1 product.


Products: Bostonscientific Zoom Latitude Prm 3120 Firmware.

## How do I fix CVE-2017-14012?

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

## Is CVE-2017-14012 being exploited?

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

## Other vulnerabilities in Boston Scientific ZOOM LATITUDE PRM

- [CVE-2017-14014](https://insights.sbomify.com/CVE-2017-14014/): Hardcoded credentials in ZOOM LATITUDE PRM (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14012 and fix it if it is affected.

What it is: CVE-2017-14012 is a medium-severity vulnerability in Boston Scientific ZOOM LATITUDE PRM, published on 1 May 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-2017-14012 in the wild and no public exploit code.

Affected product: Boston Scientific ZOOM LATITUDE PRM. 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-2017-14012/ (Markdown: https://insights.sbomify.com/CVE-2017-14012/index.md)
```

## Sources

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

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