CVE-2020-25187
No exploitation reported by the sources we read.
- Published2020-12-14
- WeaknessCWE-122 · CWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Medtronic MyCareLink Smart 25000 is vulnerable when an authenticated attacker runs a debug command, which can be sent to the patient reader and cause a heap overflow event within the MCL Smart Patient Reader software stack. The heap overflow could allow an attacker to remotely execute code on the MCL Smart Patient Reader, potentially leading to control of the device
Timeline
dates in UTC- 2020-12-1420:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-25187?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-25187?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | all versions | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Medtronic MyCareLink Smart
Smart Model 25000 Patient Reader: all versions
Fix
- Vendor fix CISA ICSMA-20-345-01 · 1 productA firmware update to eliminates these vulnerabilities has been developed by Medtronic and is available by updating the MyCareLink Smartapp via the associated mobile application store. Upgrading to the latest v5.2 mobile application version will ensure the Patient Reader is also updated on next use.…
- Vendor fix CISA ICSMA-20-345-01 · 1 productMedtronic has released additional patient focused information:
- Vendor fix CISA ICSMA-20-345-01 · 1 producthttps://www.medtronic.com/xg-en/product-security/security-bulletins.html
- Vendor fix CISA ICSMA-20-345-01 · 1 productIn response to these vulnerabilities, Medtronic has applied additional controls for monitoring and responding to improper use of the MCL Smart Patient Reader:
- Vendor fix CISA ICSMA-20-345-01 · 1 productMedtronic recommends that users take additional defensive measures to minimize risk. Specifically, users should:
- Vendor fix CISA ICSMA-20-345-01 · 1 productReport any concerning behavior regarding these products to your healthcare provider or a Medtronic representative.
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2020-12-14
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-25187?
Is CVE-2020-25187 actively exploited?
What is the CVSS score for CVE-2020-25187?
Running Medtronic MyCareLink Smart? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.