CVE-2019-18248 json
BIOTRONIK CardioMessenger II, The affected products transmit credentials in clear-text prior to switching to an encrypted communication cha…
published 6y ago modified 4mo ago also EUVD-2019-8046
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
BIOTRONIK CardioMessenger II, The affected products transmit credentials in clear-text prior to switching to an encrypted communication channel. An attacker can disclose the product’s client credentials for connecting to the BIOTRONIK Remote Communication infrastructure.
Is CVE-2019-18248 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSMA-20-170-05 updated cvss 4.3
BIOTRONIK CardioMessenger II
-
BIOTRONIK CardioMessenger II-S GSM T4APP 2.2 BIOTRONIK CardioMessenger II-S T-Line T4APP 2.2affected: 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.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 3.3 | AV:A/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-319 Cleartext Transmission of Sensitive Information
References
-
us-cert.gov
/ics/advisories/icsma-20-170-05
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-18248
- NVD CVE-2019-18248
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.