Code execution via crafted GDT file parsing
Published Jun 2, 2026 · Updated Jun 2, 2026
Out-of-bounds write in Dräger CC-Vision Basic before 7.5.3 and CC-Vision E-Cal before 7.2.5.0 allows attackers to run code via a crafted .gdt file. The .gdt parser writes beyond a destination buffer while processing attacker-controlled file content, corrupting adjacent memory. Exploitation requires a user to load or open the malicious file; the corruption can crash the application or run code with the user's privileges.
Summary
What happened
Out-of-bounds write in Dräger CC-Vision Basic before 7.5.3 and CC-Vision E-Cal before 7.2.5.0 allows attackers to run code via a crafted .gdt file. The .gdt parser writes beyond a destination buffer while processing attacker-controlled file content, corrupting adjacent memory. Exploitation requires a user to load or open the malicious file; the corruption can crash the application or run code with the user's privileges.
The record
- CVE
- CVE-2021-4478
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Dräger
- Product
- CC-Vision Basic
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- 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 <7.5.3
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