# CVE-2025-0683: Information disclosure in CMS8000 Patient Monitor

> Patient monitors leak confidential data to a hardcoded public IP in default configuration, exposing sensitive information to attackers.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-h39w-8pq5-8qh2

## What is CVE-2025-0683?

CVE-2025-0683 is a high-severity vulnerability in Contec Health CMS8000 Patient Monitor, published on 30 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In its default configuration, Contec Health CMS8000 Patient Monitor transmits plain-text 
patient data to a hard-coded public IP address when a patient is hooked 
up to the monitor. This could lead to a leakage of confidential patient 
data to any device with that IP address or an attacker in a 
machine-in-the-middle scenario.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-0683?


## How do I fix CVE-2025-0683?

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

## Is CVE-2025-0683 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0683 and fix it if it is affected.

What it is: CVE-2025-0683 is a high-severity vulnerability in Contec Health CMS8000 Patient Monitor, published on 30 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0683 in the wild and no public exploit code.

Affected product: Contec Health CMS8000 Patient Monitor. 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-2025-0683/ (Markdown: https://insights.sbomify.com/CVE-2025-0683/index.md)
```

## Sources

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

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