CVE-2021-4478
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 · uneditedDräger CC-Vision Basic before 7.5.3 and Dräger CC-Vision E-Cal before 7.2.5.0 contain an out-of-bounds write vulnerability when loading .gdt files. A crafted .gdt file can trigger a buffer overflow during file parsing, allowing an attacker to crash the application or execute malicious code on the underlying system.
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 · high confidenceDräger CC-Vision Basic and E-Cal software contain a buffer overflow vulnerability when parsing .gdt files. A specially crafted .gdt file can trigger an out-of-bounds write during file parsing, allowing an attacker to crash the application or achieve code execution on the target system.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Dräger softwareCheck Add/Remove Programs or program directory for Dräger CC-Vision Basic or Dräger CC-Vision E-Cal installationsAffected if Neither product is installed, so the vulnerability does not apply
-
Determine installed version of CC-Vision BasicCheck the program's About dialog, version info in the executable, or registry entries under HKLM\SOFTWARE\Dräger\CC-Vision BasicAffected if Version exists and is earlier than 7.5.3
-
Determine installed version of CC-Vision E-CalCheck the program's About dialog, version info in the executable, or registry entries under HKLM\SOFTWARE\Dräger\CC-Vision E-CalAffected if Version exists and is earlier than 7.2.5.0
-
Verify .gdt file handling capabilityConfirm the application includes .gdt file import or parsing functionality by checking file association settings or the application's supported file typesAffected if The application can import or open .gdt files, which is the attack vector for this vulnerability
You are affected if you have CC-Vision Basic earlier than 7.5.3 or CC-Vision E-Cal earlier than 7.2.5.0, and the application can process .gdt files.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate Dräger CC-Vision Basic to version 7.5.3 or later, and Dräger CC-Vision E-Cal to version 7.2.5.0 or later. Avoid opening untrusted .gdt files until updates are applied.
Dräger CC-Vision Basic 7.5.3 or later; Dräger CC-Vision E-Cal 7.2.5.0 or later
- 1. Identify which Dräger CC-Vision product is installed: CC-Vision Basic or CC-Vision E-Cal
- 2. Check the current installed version of the software (typically available in the About/Help section of the application)
- 3. For CC-Vision Basic users: Upgrade to version 7.5.3 or later
- 4. For CC-Vision E-Cal users: Upgrade to version 7.2.5.0 or later
- 5. Obtain the update from the official Dräger source at static.draeger.com or through your Dräger service representative
- 6. After upgrading, verify the new version is correctly installed
- 7. Test that legitimate .gdt file loading still functions properly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-4478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-4478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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