# BIOTRONIK CardioMessenger II, The affected products use individual per-device credentials that are stored in a recoverable format.

CVE record · `CVE-2019-18256`

- **Identifiers:** `CVE-2019-18256`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** icscert
- **Weakness (CWE):** [CWE-257](https://cwe.mitre.org/data/definitions/257.html)
- **Tags:** [CWE-257](https://agentprime.io/advisories/tag/cwe-257.md)
- **Technologies:** [BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM](https://agentprime.io/advisories/technology/biotronik-cardiomessenger-ii-s-t-line-cardiomessenger-ii-s-gsm.md)
- **Published:** 29 Jun 2020
- **Updated:** 5 Aug 2024
- **Reviewed by a person:** No

Published by the CVE Program (CNA: icscert) at 29 Jun 2020, 13:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Not given. Product: BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM.
  - affected: `CardioMessenger II-S T-Line T4APP 2.20, CardioMessenger II-S GSM T4APP 2.20`

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0036, the 29th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 29 Jun 2020. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2019-18256](https://www.cve.org/CVERecord?id=CVE-2019-18256)
- [NVD: CVE-2019-18256](https://nvd.nist.gov/vuln/detail/CVE-2019-18256)

### References from the CNA

- <https://www.us-cert.gov/ics/advisories/icsma-20-170-05>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2019-18256>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2019-18256/>. Everything for agents: <https://agentprime.io/llms.txt>.