dbcve.org
DrivelockApplication

CVE-2025-67794

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 24.2.8 / 25.1.6 or later.
See remediation →
63/100
Remediation priority · Elevated
Zero-click

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
An issue was discovered in DriveLock 24.1 through 24.1.*, 24.2 before 24.2.8, and 25.1 before 25.1.6. Directories and files created by the agent are created with overly permissive ACLs, allowing local users without administrator rights to trigger actions or destabilize the agent.

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

DriveLock agent versions 24.1 through 24.1.*, 24.2 before 24.2.8, and 25.1 before 25.1.6 create directories and files with overly permissive Access Control Lists (ACLs). This allows local non-privileged users to read, modify, or delete agent-created files, potentially enabling them to trigger unauthorized actions or destabilize the security agent.

MitigationApply the vendor-supplied patches (24.2.8 or 25.1.6 depending on the version branch in use) to remediate the improper ACL configuration on agent-created files and directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DrivelockApplication
Affected:>= 24.1, <= 24.1.4>= 24.2, < 24.2.8>= 25.1, < 25.1.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

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 DriveLock agent installation and version
    Use the system package manager or check installed programs to determine if DriveLock agent is installed and retrieve its version number (for example, run 'Get-Package -Name *DriveLock*' or check the installed software list in Windows Registry)
    Affected if The installed version falls within 24.1.x (through 24.1.4), 24.2.x (before 24.2.8), or 25.1.x (before 25.1.6)
  2. Locate DriveLock agent-created directories
    Identify directories created by the DriveLock agent on the system. These are typically found in program data or application directories used by the security agent. Check common locations such as installation folders and data directories.
    Affected if DriveLock agent directories exist on the system and the installed version is in the affected range
  3. Inspect ACL permissions on DriveLock directories
    Use icacls or a similar tool to examine the Access Control Lists on directories created by the DriveLock agent. Run 'icacls <directory_path>' to view all permission entries.
    Affected if The ACLs grant read, modify, or delete permissions to non-privileged users or groups (such as Users or Everyone) on agent-created directories
  4. Inspect ACL permissions on DriveLock files
    Use icacls or a similar tool to examine the Access Control Lists on files created by the DriveLock agent. Check both configuration files and runtime files created by the agent.
    Affected if The ACLs grant write or delete permissions to non-privileged users on agent-created files, which could allow unauthorized modification or deletion

The system is affected if DriveLock agent version 24.1.x through 24.1.4, 24.2.x before 24.2.8, or 25.1.x before 25.1.6 is installed AND the agent-created directories or files have overly permissive ACLs that allow non-privileged users to read, modify, or delete them.

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
Upgrade available Upgrade to 24.2.8 / 25.1.6 or later
Fixed in 24.2.825.1.6
Interim mitigation

Apply the vendor-supplied patches (24.2.8 or 25.1.6 depending on the version branch in use) to remediate the improper ACL configuration on agent-created files and directories.

Recommended fix High confidence

24.2.8 or 25.1.6 (depending on which major version line you are on)

  1. Identify the currently installed DriveLock version by checking the agent or control panel
  2. For DriveLock 24.1.x users: Upgrade to version 24.2.8 or later (24.1.x line is no longer supported)
  3. For DriveLock 24.2.x users: Upgrade to version 24.2.8 or later
  4. For DriveLock 25.1.x users: Upgrade to version 25.1.6 or later
  5. Verify the upgrade was successful by checking the new version number
  6. Test that the agent functions normally after upgrade
Caveat Minimal risk - this is a patch release addressing ACL permissions; ensure compatibility with your current Windows environment before deploying

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

Fix this in Drivelock Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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