SDC processing halt via malformed discovery messages
Published Jun 2, 2026 · Updated Jun 2, 2026
Resource exhaustion in Dräger Core 1.0.5 and earlier and M540 Converter Service 1.0.9 and earlier allows remote attackers to halt SDC processing. Malformed, unencrypted SDC messages sent during discovery drive the affected process to high CPU load until it stops handling later SDC messages. Access to the hospital network is required, and the documented consequence is loss of SDC message processing rather than data disclosure or modification.
Summary
What happened
Resource exhaustion in Dräger Core 1.0.5 and earlier and M540 Converter Service 1.0.9 and earlier allows remote attackers to halt SDC processing. Malformed, unencrypted SDC messages sent during discovery drive the affected process to high CPU load until it stops handling later SDC messages. Access to the hospital network is required, and the documented consequence is loss of SDC message processing rather than data disclosure or modification.
The record
- CVE
- CVE-2024-14036
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Dräger
- Product
- Core
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo