# CVE-2019-18252: Information disclosure in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM

> An attacker with adjacent access can disclose credentials used for remote communication, potentially enabling unauthorized access to the BIOTRONIK infrastructure.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2f8f-gw52-m98c

## What is CVE-2019-18252?

CVE-2019-18252 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.

### Official description

BIOTRONIK CardioMessenger II, The affected products allow credential reuse for multiple authentication purposes. An attacker with adjacent access to the CardioMessenger can disclose its credentials used for connecting to the BIOTRONIK Remote Communication infrastructure.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-18252?

It affects 2 products.


Products: Biotronik Cardiomessenger Ii-S Gsm Firmware, Biotronik Cardiomessenger Ii-S T-Line Firmware.

## How do I fix CVE-2019-18252?

No fix has been published for CVE-2019-18252 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-18252 being exploited?

There is no known exploitation of CVE-2019-18252 in the wild and no public exploit code.

## Other vulnerabilities in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM

- [CVE-2019-18254](https://insights.sbomify.com/CVE-2019-18254/): Information disclosure in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM (medium 4.6)
- [CVE-2019-18256](https://insights.sbomify.com/CVE-2019-18256/): Hardcoded credentials in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM (medium 4.6)
- [CVE-2019-18246](https://insights.sbomify.com/CVE-2019-18246/): Auth bypass in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM (medium 4.3)
- [CVE-2019-18248](https://insights.sbomify.com/CVE-2019-18248/): Information disclosure in BIOTRONIK CardioMessenger II-S T-Line, CardioMessenger II-S GSM (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18252 and fix it if it is affected.

What it is: CVE-2019-18252 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.
Exploitation: There is no known exploitation of CVE-2019-18252 in the wild and no public exploit code.

Affected 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.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-18252/ (Markdown: https://insights.sbomify.com/CVE-2019-18252/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-18252
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-18252
- OSV: https://osv.dev/vulnerability/CVE-2019-18252

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-18252/
Summaries are generated and may contain mistakes; the official description above is the record.