{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-18256 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18256 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18256 is a medium-severity vulnerability in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18256 and fix it if it is affected.\n\nWhat it is: CVE-2019-18256 is a medium-severity vulnerability in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-18256 in the wild and no public exploit code.\n\nAffected product: BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM. 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-2019-18256/ (Markdown: https://insights.sbomify.com/CVE-2019-18256/index.md)","id":"CVE-2019-18256","markdown":"https://insights.sbomify.com/CVE-2019-18256/index.md","name":"CVE-2019-18256","record":{"aliases":["GHSA-qhvv-89m3-h89m"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Medical device","requires_auth":"none","summary":"Attackers with physical access can extract recoverable credentials to authenticate and decrypt local data in transit on CardioMessenger devices.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"cardiomessenger_ii-s_gsm_firmware","vendor":"biotronik"},{"product":"cardiomessenger_ii-s_t-line_firmware","vendor":"biotronik"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-257","name":"Storing Passwords in a Recoverable Format"}],"description":"BIOTRONIK CardioMessenger II, The affected products use individual per-device credentials that are stored in a recoverable format. An attacker with physical access to the CardioMessenger can use these credentials for network authentication and decryption of local data in transit.","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":"Hardcoded credentials in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM","id":"CVE-2019-18256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Advantech DiagAnywhere Server","id":"CVE-2019-18257"},"packages":[],"prev":{"headline":"Privilege escalation in HMI/SCADA iFIX","id":"CVE-2019-18255"},"products":["BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM"],"published":"2020-06-29","related":[{"cvss_score":4.6,"headline":"Information disclosure in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM","id":"CVE-2019-18254","kev_date_added":null,"published":"2020-06-29"},{"cvss_score":4.3,"headline":"Auth bypass in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM","id":"CVE-2019-18246","kev_date_added":null,"published":"2020-06-29"},{"cvss_score":4.3,"headline":"Information disclosure in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM","id":"CVE-2019-18248","kev_date_added":null,"published":"2020-06-29"},{"cvss_score":4.3,"headline":"Information disclosure in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM","id":"CVE-2019-18252","kev_date_added":null,"published":"2020-06-29"}],"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":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with physical access can extract recoverable credentials to authenticate and decrypt local data in transit on CardioMessenger devices.","url":"https://insights.sbomify.com/CVE-2019-18256/"}