# CVE-2019-25722: Dräger SC Monitoring Devices Hard-coded Credentials and DoS

> Attackers can use hard-coded credentials to alter device configuration or send malformed packets to cause denial of service in Dräger SC monitoring devices.

- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA: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:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-fh3f-j952-25x6

## What is CVE-2019-25722?

CVE-2019-25722 is a high-severity vulnerability in Dräger SC 6002XL, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dräger SC Monitoring devices (SC 6002XL, SC 6802XL, SC 7000, SC 8000, SC 9000 XL) contain hard-coded plaintext credentials in source code and a denial-of-service vulnerability that allows local and remote attackers to compromise device integrity across all software versions. A local attacker with direct device access can use the hard-coded credentials to access service and clinical accounts and alter device configuration, while a remote attacker can send malformed network packets to cause repeated device reboots, ultimately resulting in loss of network connectivity and disruption of patient monitoring.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2019-25722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25722 is a high-severity vulnerability in Dräger SC 6002XL, published on 2 Jun 2026. 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-25722 in the wild and no public exploit code.

Affected product: Dräger SC 6002XL. 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-25722/ (Markdown: https://insights.sbomify.com/CVE-2019-25722/index.md)
```

## Sources

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

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