CVE-2019-6538· NVD / CVE Program· CNA icscert

Medtronic Conexus Radio Frequency Telemetry Protocol Improper Access Control

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.89% (FIRST EPSS); higher than 58.8% of all records.
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Severity is disputed: the assigning authority (CNA) scores it 9.3, NVD 6.5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The Conexus telemetry protocol utilized within Medtronic MyCareLink Monitor versions 24950 and 24952, CareLink Monitor version 2490C, CareLink 2090 Programmer, Amplia CRT-D, Claria CRT-D, Compia CRT-D, Concerto CRT-D, Concerto II CRT-D, Consulta CRT-D, Evera ICD, Maximo II CRT-D and ICD, Mirro ICD, Nayamed ND ICD, Primo ICD, Protecta ICD and CRT-D, Secura ICD, Virtuoso ICD, Virtuoso II ICD, Visia AF ICD, and Viva CRT-D does not implement authentication or authorization. An attacker with adjacent short-range access to an affected product, in situations where the product’s radio is turned on, can inject, replay, modify, and/or intercept data within the telemetry communication. This communication protocol provides the ability to read and write memory values to affected implanted cardiac devices; therefore, an attacker could exploit this communication protocol to change memory in the implanted cardiac device.

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

Published: Mar 25, 2019
Updated: Jun 16, 2026
EPSS: 0.8% · 58th percentile
CWE: CWE-284

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.8%

CNA vs NVD score

NVD: 6.5
CNA · icscert: 9.3; 2.8 point gap

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
medtronic	mycarelink monitor firmware	cpe:2.3:o:medtronic:mycarelink_monitor_firmware
medtronic	mycarelink monitor	cpe:2.3:h:medtronic:mycarelink_monitor
medtronic	carelink monitor firmware	cpe:2.3:o:medtronic:carelink_monitor_firmware
medtronic	carelink monitor	cpe:2.3:h:medtronic:carelink_monitor
medtronic	carelink 2090 firmware	cpe:2.3:o:medtronic:carelink_2090_firmware
medtronic	carelink 2090	cpe:2.3:h:medtronic:carelink_2090
medtronic	amplia crt-d firmware	cpe:2.3:o:medtronic:amplia_crt-d_firmware
medtronic	amplia crt-d	cpe:2.3:h:medtronic:amplia_crt-d
medtronic	claria crt-d firmware	cpe:2.3:o:medtronic:claria_crt-d_firmware
medtronic	claria crt-d	cpe:2.3:h:medtronic:claria_crt-d
medtronic	compia crt-d firmware	cpe:2.3:o:medtronic:compia_crt-d_firmware
medtronic	compia crt-d	cpe:2.3:h:medtronic:compia_crt-d

and 28 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

medtronic amplia crt-d firmwareall versions
medtronic carelink 2090 firmwareall versions
medtronic carelink monitor firmware2490c
medtronic claria crt-d firmwareall versions
medtronic compia crt-d firmwareall versions
medtronic concerto crt-d firmwareall versions
medtronic concerto ii crt-d firmwareall versions
medtronic consulta crt-d firmwareall versions
medtronic evera icd firmwareall versions
medtronic maximo ii crt-d and lcd firmwareall versions
medtronic mirro icd firmwareall versions
medtronic mycarelink monitor firmware24950
medtronic mycarelink monitor firmware24952
medtronic nayamed nd icd firmwareall versions
medtronic primo icd firmwareall versions
medtronic protecta icd and crt-d firmwareall versions
medtronic secura icd firmwareall versions
medtronic virtuoso icd firmwareall versions
medtronic virtuoso ii icd firmwareall versions
medtronic visia af icd firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.

Medtronic Amplia CRT-D
- All versionsaffected
Medtronic Brava CRT-D
- All versionsaffected
Medtronic CareLink 2090 Programmer
- All versionsaffected
Medtronic CareLink Monitor
- 2490Caffected
Medtronic Claria CRT-D
- All versionsaffected
Medtronic Compia CRT-D
- All versionsaffected
Medtronic Concerto CRT-D
- All versionsaffected
Medtronic Concerto II CRT-D
- All versionsaffected
Medtronic Conexus Radio Frequency Telemetry Protocol
- All versionsaffected
Medtronic Consulta CRT-D
- All versionsaffected
Medtronic Evera ICD
- All versionsaffected
Medtronic Maximo II CRT-D
- All versionsaffected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Peter MorganClever Security; Dave Singelée and Bart Preneel of KU Leuven; Eduard Marin formerlyfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).