# CVE-2024-14036: Dräger Core 1.0.5 Denial of Service via Malformed SDC Message

> Network-adjacent attackers can cause denial of service in Dräger Core and M540 Converter Service by sending malformed SDC messages, exhausting CPU resources.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-f3qj-wr66-g552

## What is CVE-2024-14036?

CVE-2024-14036 is a high-severity denial of service vulnerability in Dräger Core, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dräger Core 1.0.5 and Dräger M540 Converter Service 1.0.9 contain a denial of service vulnerability that allows network-adjacent attackers to trigger high CPU load by sending specially crafted, unencrypted SDC messages during the discovery process. Attackers with access to the hospital network can send malformed SDC packets to exhaust CPU resources in the affected process, causing further SDC messages to no longer be processed.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-14036?


## How do I fix CVE-2024-14036?

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

## Is CVE-2024-14036 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-14036 and fix it if it is affected.

What it is: CVE-2024-14036 is a high-severity denial of service vulnerability in Dräger Core, published on 2 Jun 2026. 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-2024-14036 in the wild and no public exploit code.

Affected product: Dräger Core. 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-2024-14036/ (Markdown: https://insights.sbomify.com/CVE-2024-14036/index.md)
```

## Sources

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

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