2090 Carelink Programmer Firmware
Approved changes feed: RSS · Atom
cpe:2.3:o:medtronic:2090_carelink_programmer_firmware:*:*:*:*:*:*:*:*
part: o version: * update: *
| Vendor | Medtronic (39ade870-5d3b-575a-9a52-512cca95c641) |
|---|---|
| Product | 2090 Carelink Programmer Firmware (4fa66605-0fd8-5f98-8b07-df67f2d52824) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-5448 |
vulnerable | 2026-06-08 05:11:51.049643 |
Medtronic 2090 Carelink Programmer Relative Path Traversal
MEDIUM (4.8)
Medtronic 2090 CareLink Programmer’s software deployment network contains a directory traversal vulnerability that could allow an attacker to read files on the system.
Published: 2018-05-04T18:00:00.000Z
Updated: 2025-05-22T17:43:06.800Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-5446 |
vulnerable | 2026-06-08 05:11:51.045930 |
Medtronic 2090 Carelink Programmer Storing Passwords in a Recoverable Format
MEDIUM (4.9)
Medtronic 2090 CareLink Programmer
uses a per-product username and password that is stored in a recoverable format.
Published: 2018-05-04T18:00:00.000Z
Updated: 2025-05-22T17:40:34.569Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-10596 |
vulnerable | 2026-06-08 05:10:35.121266 |
Medtronic 2090 Carelink Programmer Improper Restriction of Communication Channel to Intended Endpoints
HIGH (7.1)
Medtronic 2090 CareLink Programmer
uses a virtual private network connection to securely download updates. It does not verify it is still connected to this virtual private network before downloading updates. The affected products initially establish an encapsulated IP-based VPN connection to a Medtronic-hosted update network. Once the VPN is established, it makes a request to a HTTP (non-TLS) server across the VPN for updates, which responds and provides any available updates. The programmer-side (client) service responsible for this HTTP request does not check to ensure it is still connected to the VPN before making the HTTP request. Thus, an attacker could cause the VPN connection to terminate (through various methods and attack points) and intercept the HTTP request, responding with malicious updates via a man-in-the-middle attack. The affected products do not verify the origin or integrity of these updates, as it insufficiently relied on the security of the VPN. An attacker with remote network access to the programmer could influence these communications.
Published: 2018-07-02T18:00:00.000Z
Updated: 2025-05-22T17:36:04.656Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.