BIOTRONIK CardioMessenger II, The affected products do not encrypt sensitive information while at rest.

published 2020-06-29 6y ago modified 2026-06-17 4mo ago also EUVD-2019-8052

cvss: 4.6; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits: 0; none known

BIOTRONIK CardioMessenger II, The affected products do not encrypt sensitive information while at rest. An attacker with physical access to the CardioMessenger can disclose medical measurement data and the serial number from the implanted cardiac device the CardioMessenger is paired with.

Is CVE-2019-18254 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-20-170-05 updated 2020-06-18 cvss 4.6

BIOTRONIK CardioMessenger II

BIOTRONIK CardioMessenger II-S GSM T4APP 2.2 BIOTRONIK CardioMessenger II-S T-Line T4APP 2.2
affected: vendor fix

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.6	CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

n/a BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM

Classification

Weakness

CWE-311 Missing Encryption of Sensitive Data
CWE-312 Cleartext Storage of Sensitive Information

References

us-cert.gov /ics/advisories/icsma-20-170-05
third-party-advisory, us-government-resource

Sources

CVE List CVE-2019-18254
NVD CVE-2019-18254

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.