Credential exposure via recoverable on-device storage
Published Jun 29, 2020 · Updated Aug 5, 2024
Credential exposure in BIOTRONIK CardioMessenger II-S firmware 2.20 allows physically proximate attackers to obtain device credentials. The transmitter stores individual per-device credentials in recoverable form in memory exposed after its housing is opened. Physical possession is required; the credentials support network authentication and decryption of locally intercepted traffic but do not permit implant reprogramming.
Summary
What happened
Credential exposure in BIOTRONIK CardioMessenger II-S firmware 2.20 allows physically proximate attackers to obtain device credentials. The transmitter stores individual per-device credentials in recoverable form in memory exposed after its housing is opened. Physical possession is required; the credentials support network authentication and decryption of locally intercepted traffic but do not permit implant reprogramming.
The record
- CVE
- CVE-2019-18256
- Published
- Jun 29, 2020
- Updated
- Aug 5, 2024
- Vendor
- BIOTRONIK
- Product
- CardioMessenger II-S
- Classifications
- CWE-257, CWE-522, CAPEC-49, T1555
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=CardioMessenger II-S T-Line T4APP 2.20, CardioMessenger II-S GSM T4APP 2.20
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo