CVE-2019-25722
Hard-Coded Credentials and DoS in Dräger SC Monitoring Devices
Publication date: 2026-06-02
Last updated on: 2026-06-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dräger | sc_monitoring_devices | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-798 | The product contains hard-coded credentials, such as a password or cryptographic key. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
Dräger SC Monitoring devices, including models SC 6002XL, SC 6802XL, SC 7000, SC 8000, and SC 9000 XL, have two main vulnerabilities. First, they contain hard-coded plaintext credentials in their source code, which means attackers with direct access to the device can use these credentials to access service and clinical accounts and change device configurations. Second, there is a denial-of-service (DoS) vulnerability that allows both local and remote attackers to send malformed network packets, causing the devices to reboot repeatedly. This disrupts network connectivity and patient monitoring.
How can this vulnerability impact me? :
This vulnerability can severely impact the integrity and reliability of Dräger SC Monitoring devices. A local attacker with physical access can compromise critical service and clinical accounts, potentially altering device configurations and affecting device operation. Remote attackers can exploit the denial-of-service vulnerability to cause repeated device reboots, leading to loss of network connectivity and disruption of patient monitoring. Such disruptions can compromise patient safety and the effectiveness of clinical monitoring.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability involves hard-coded plaintext credentials in the device source code and a denial-of-service vulnerability triggered by malformed network packets causing device reboots.
Detection on your network or system would involve checking for the presence of affected Dräger SC Monitoring devices (models SC 6002XL, SC 6802XL, SC 7000, SC 8000, SC 9000 XL) and monitoring for unusual device reboots or disruptions in patient monitoring.
Since the credentials are hard-coded in the source code, detection might require physical or direct access to the device to verify the presence of these credentials.
For network detection, monitoring for malformed network packets targeting these devices could help identify exploitation attempts.
Specific commands are not provided in the available resources, so no exact commands can be suggested.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting physical and network access to the affected Dräger SC Monitoring devices to prevent unauthorized local or remote access.
Monitor the devices for signs of repeated reboots or network disruptions that may indicate exploitation attempts.
Coordinate with Dräger for any available security updates or patches, as they handle vulnerability disclosures and fixes.
Implement network-level protections such as firewalls or intrusion detection systems to block malformed packets that could trigger the denial-of-service condition.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Dräger SC Monitoring devices involves hard-coded plaintext credentials and a denial-of-service issue that can compromise device integrity and disrupt patient monitoring. Such security weaknesses can potentially impact compliance with standards and regulations like GDPR and HIPAA, which require protection of sensitive data and ensure the availability and integrity of medical devices and patient information.
Specifically, unauthorized access through hard-coded credentials could lead to unauthorized alteration of device configurations and possible exposure or manipulation of clinical data, which conflicts with data protection requirements under GDPR and HIPAA. Additionally, the denial-of-service vulnerability causing device reboots and loss of network connectivity could disrupt patient monitoring, affecting the reliability and availability mandates of these regulations.
However, the provided resources do not explicitly discuss compliance impacts or mitigation strategies related to these regulations.