dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2024-12248

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Contec Health CMS8000 Patient Monitor is vulnerable to an out-of-bounds write, which could allow an attacker to send specially formatted UDP requests in order to write arbitrary data. This could result in remote code execution.

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

Out-of-bounds write vulnerability in Contec Health CMS8000 Patient Monitor allows remote attackers to send specially crafted UDP packets to write arbitrary data to memory, potentially achieving remote code execution.

MitigationIsolate patient monitors on dedicated network segments with strict firewall rules limiting UDP traffic, and coordinate with Contec Health for official firmware patches; network segmentation serves as a critical compensating control 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the device model
    Check the device label, system information, or network scan for 'CMS8000' or 'Contec Health' patient monitor branding
    Affected if The device is a Contec Health CMS8000 Patient Monitor
  2. Verify UDP service exposure
    Scan the device network port using 'nc -z -u <device_ip> <port>' or UDP scanner to confirm UDP services are accessible from your network
    Affected if UDP ports on the device are reachable from an untrusted network segment
  3. Check firmware version
    Access the device admin interface or check via SNMP/ssh: 'show version' or similar command depending on available management interfaces
    Affected if The firmware version is any version of the CMS8000 Patient Monitor (no specific version range provided)
  4. Review network segmentation
    Verify if the device is on a dedicated medical device VLAN by checking network switch configuration or firewall rules
    Affected if The device shares a network segment with untrusted systems or is directly accessible from general infrastructure

You are affected if you operate a Contec Health CMS8000 Patient Monitor with exposed UDP network services accessible from non-segmented networks

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

Isolate patient monitors on dedicated network segments with strict firewall rules limiting UDP traffic, and coordinate with Contec Health for official firmware patches; network segmentation serves as a critical compensating control while awaiting vendor remediation.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12248 — 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-2024-12248 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