{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25187 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25187 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25187 is a high-severity memory corruption vulnerability in Medtronic Smart Model 25000 Patient Reader, published on 14 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-25187 and fix it if it is affected.\n\nWhat it is: CVE-2020-25187 is a high-severity memory corruption vulnerability in Medtronic Smart Model 25000 Patient Reader, published on 14 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-25187 in the wild and no public exploit code.\n\nAffected product: Medtronic Smart Model 25000 Patient Reader. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-25187/ (Markdown: https://insights.sbomify.com/CVE-2020-25187/index.md)","id":"CVE-2020-25187","markdown":"https://insights.sbomify.com/CVE-2020-25187/index.md","name":"CVE-2020-25187","record":{"aliases":["GHSA-4m4f-3m29-78r8"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Medtronic patient reader","requires_auth":"none","summary":"An authenticated attacker can trigger a heap overflow via debug commands to remotely execute code and control the Medtronic MyCareLink Smart Patient Reader.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"mycarelink_smart_model_25000_firmware","vendor":"medtronic"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Medtronic MyCareLink Smart 25000 is \n\n 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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Medtronic MyCareLink Smart Heap-based Buffer Overflow","id":"CVE-2020-25187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in LAquis SCADA","id":"CVE-2020-25188"},"packages":[],"prev":{"headline":"XML external entity in WECON Technology Co., Ltd (WECON) LeviStudioU","id":"CVE-2020-25186"},"products":["Smart Model 25000 Patient Reader"],"published":"2020-12-14","related":[{"cvss_score":8.8,"headline":"Medtronic MyCareLink Smart Time-of-check Time-of-use Race Condition","id":"CVE-2020-27252","kev_date_added":null,"published":"2020-12-14"},{"cvss_score":8,"headline":"Medtronic MyCareLink Smart Improper Authentication","id":"CVE-2020-25183","kev_date_added":null,"published":"2020-12-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-05-22","vendors":["Medtronic"]},"summary":"An authenticated attacker can trigger a heap overflow via debug commands to remotely execute code and control the Medtronic MyCareLink Smart Patient Reader.","url":"https://insights.sbomify.com/CVE-2020-25187/"}