dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2019-25722

HIGH · 7.6 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Dräger SC Monitoring devices contain hard-coded plaintext credentials embedded in source code, allowing local attackers with direct device access to authenticate to service and clinical accounts and modify device configuration. Additionally, a denial-of-service vulnerability permits remote attackers to send malformed network packets triggering repeated device reboots, resulting in loss of network connectivity and disruption of patient monitoring capabilities.

MitigationContact Dräger for available firmware updates or security patches; implement network segmentation and access controls to limit exposure to unauthenticated network attacks while awaiting vendor remediation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Locate the device label, system information screen, or boot sequence output to confirm the exact model number (SC 6002XL, SC 6802XL, SC 7000, SC 8000, or SC 9000 XL)
    Affected if Device model is one of the listed affected models
  2. Determine firmware version
    Access device system settings, maintenance menu, or boot diagnostics to retrieve the installed firmware version number
    Affected if Firmware version is unpatched and matches the affected release; compare against any vendor-released patch versions if available
  3. Inspect for hardcoded credentials
    Examine device configuration files, service menus, or access logs for any embedded plaintext usernames/passwords used for service or clinical accounts
    Affected if Hardcoded credentials are present in device configuration or accessible through service interfaces
  4. Verify console port accessibility
    Check physical security and network access to device console (serial/USB) ports - determine if unauthorized physical access is possible
    Affected if Console ports are physically accessible to untrusted personnel without monitoring
  5. Assess network exposure
    Review network segmentation, firewall rules, and device IP configuration to determine if the device is directly reachable from network segments outside isolated medical device VLANs
    Affected if Device is reachable from non-segmented networks and may accept malformed network packets
  6. Monitor for reboot anomalies
    Check device event logs, network monitoring tools, or uptime records for unexpected restart cycles or loss-of-connectivity events
    Affected if Device exhibits repeated unexplained reboots or periodic network dropouts

A defender is affected if they operate any SC 6002XL, SC 6802XL, SC 7000, SC 8000, or SC 9000 XL device with vulnerable firmware where console ports are accessible or the device is network-exposed without isolation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact Dräger for available firmware updates or security patches; implement network segmentation and access controls to limit exposure to unauthenticated network attacks while awaiting vendor remediation.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-25722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-25722 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data