{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10596 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10596 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10596 is a high-severity vulnerability in Medtronic 2090 CareLink Programmer, published on 2 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-10596 and fix it if it is affected.\n\nWhat it is: CVE-2018-10596 is a high-severity vulnerability in Medtronic 2090 CareLink Programmer, published on 2 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-10596 in the wild and no public exploit code.\n\nAffected product: Medtronic 2090 CareLink Programmer. 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-2018-10596/ (Markdown: https://insights.sbomify.com/CVE-2018-10596/index.md)","id":"CVE-2018-10596","markdown":"https://insights.sbomify.com/CVE-2018-10596/index.md","name":"CVE-2018-10596","record":{"aliases":["GHSA-3vcw-xhqc-97mh"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Medtronic CareLink Programmer","requires_auth":"low_privilege","summary":"An attacker can intercept unencrypted update requests if the VPN drops, allowing malicious code execution on Medtronic programmers.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"2090_carelink_programmer_firmware","vendor":"medtronic"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"},{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"Medtronic 2090 CareLink Programmer \n\nuses 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.","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 2090 Carelink Programmer Improper Restriction of Communication Channel to Intended Endpoints","id":"CVE-2018-10596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors","id":"CVE-2018-10597"},"packages":[],"prev":{"headline":"SQL injection in Kiestra and InoqulA systems","id":"CVE-2018-10595"},"products":["2090 CareLink Programmer","29901 Encore Programmer"],"published":"2018-07-02","related":[{"cvss_score":4.9,"headline":"Medtronic 2090 Carelink Programmer Storing Passwords in a Recoverable Format","id":"CVE-2018-5446","kev_date_added":null,"published":"2018-05-04"},{"cvss_score":4.8,"headline":"Medtronic 2090 Carelink Programmer Relative Path Traversal","id":"CVE-2018-5448","kev_date_added":null,"published":"2018-05-04"}],"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 attacker can intercept unencrypted update requests if the VPN drops, allowing malicious code execution on Medtronic programmers.","url":"https://insights.sbomify.com/CVE-2018-10596/"}