dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2021-4481

HIGH · 8.2 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
85/100
Remediation priority · High
No privileges

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
Dräger Protector Software prior to version 6.4.2 contains a local privilege escalation vulnerability due to insecure file system permissions that allows local attackers to execute arbitrary code with elevated privileges. Attackers can replace binaries or loaded modules on the host system to execute code with NT SYSTEM privileges.

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 confidence

Dräger Protector Software versions prior to 6.4.2 have insecure file system permissions that allow local attackers to replace binaries or loaded modules on the host system, enabling arbitrary code execution with NT SYSTEM privileges.

MitigationUpgrade Dräger Protector Software to version 6.4.2 or later and verify that file system permissions on application directories are properly configured to prevent unauthorized binary replacement.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dräger Protector Software version
    Locate the Dräger Protector Software installation on the system and check the version information (typically found in the application properties, an about dialog, or the executable's file version metadata). Compare the installed version to the affected range (any version prior to 6.4.2).
    Affected if The installed version is earlier than 6.4.2 (for example, 6.4.1, 6.4.0, or any prior release).
  2. Locate the application installation directory
    Find the directory where Dräger Protector Software is installed. This is typically found in Program Files or a custom installation path chosen during setup.
    Affected if The application directory exists on the system, indicating Dräger Protector Software is installed.
  3. Verify file system permissions on executable files
    Inspect the file system permissions on the Dräger Protector Software installation directory, specifically focusing on executable files (.exe) and DLL files. Useicacls or Get-Acl to check which users and groups have Write or Modify access to these files.
    Affected if Unprivileged users (non-administrators) have Write or Modify permissions to executable files or loaded modules within the application directory.
  4. Verify file system permissions on loaded modules
    Check permissions on all DLL files and other loaded modules used by the application. Ensure that standard users cannot replace or modify these library files.
    Affected if Unprivileged users have the ability to modify or replace DLL files or other modules loaded by the application.

You are affected if Dräger Protector Software version prior to 6.4.2 is installed AND unprivileged users have Write or Modify access to executable files or loaded modules in the application directory, allowing potential code execution with elevated privileges.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Dräger Protector Software to version 6.4.2 or later and verify that file system permissions on application directories are properly configured to prevent unauthorized binary replacement.

Recommended fix High confidence

Dräger Protector Software version 6.4.2

  1. Obtain Dräger Protector Software version 6.4.2 or later from the official Dräger source (static.draeger.com or authorized Dräger distribution channels)
  2. Review Dräger's release notes and upgrade documentation for version 6.4.2
  3. Ensure you have a valid backup of the current system and data
  4. Schedule a maintenance window for the upgrade process
  5. Stop all Dräger Protector Software services and related processes
  6. Upgrade Dräger Protector Software to version 6.4.2 by running the installer with appropriate administrative privileges
  7. Verify that the file system permissions on binaries and loaded modules have been corrected in the new version
  8. Restart the Dräger Protector Software services

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA3.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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