dbcve.org
DrivelockApplication

CVE-2025-67781

CRITICAL · 9.9 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 24.1.6 / 24.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5. Local unprivileged users can manipulate privileged processes to gain more privileges on Windows computers.

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 · moderate confidence

A local privilege escalation vulnerability in DriveLock security software allows unprivileged Windows users to manipulate privileged processes, enabling them to gain elevated (administrator/SYSTEM) privileges on the affected system.

MitigationApply vendor patches by upgrading to DriveLock version 24.1.6 or later, 24.2.7 or later, or 25.1.5 or later.

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.6>= 24.2, < 24.2.7>= 25.1, < 25.1.5

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 DriveLock version
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\DriveLock or check the version in Add or Remove Programs. Alternatively, right-click the DriveLock icon in the system tray and select About or Help > About.
    Affected if The installed version is 24.1.x where x is less than 6, OR 24.2.x where x is less than 7, OR 25.1.x where x is less than 5.
  2. Verify DriveLock service is running
    Open Services console (services.msc) and locate the DriveLock service, or run 'Get-Service -Name *DriveLock*' in PowerShell.
    Affected if The DriveLock service is running and the version from step 1 falls within the vulnerable ranges.
  3. Check for unprivileged user write access to DriveLock installation directory
    Open File Explorer, navigate to the DriveLock installation folder (typically C:\Program Files\DriveLock or C:\Program Files (x86)\DriveLock), right-click the folder, select Properties > Security, and verify if Users or authenticated users have Write or Modify permissions.
    Affected if Non-admin users have Write/Modify permissions to DriveLock program files AND the version is vulnerable.
  4. Review DriveLock driver status
    Open an elevated Command Prompt and run 'sc query Drivelock' or 'driverquery /v | findstr -i Drivelock' to check if the DriveLock kernel driver is loaded.
    Affected if The driver is loaded and the installed version is in the vulnerable range.

A user is affected if DriveLock version is 24.1.0-24.1.5, 24.2.0-24.2.6, or 25.1.0-25.1.4, AND the DriveLock service or driver is active on the system.

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.1.6 / 24.2.7 / 25.1.5 or later
Fixed in 24.1.624.2.725.1.5
Interim mitigation

Apply vendor patches by upgrading to DriveLock version 24.1.6 or later, 24.2.7 or later, or 25.1.5 or later.

Recommended fix High confidence

Upgrade to 24.1.6 (for 24.1.x), 24.2.7 (for 24.2.x), or 25.1.5 (for 25.1.x) depending on your current major version branch

  1. Identify the currently installed DriveLock version by checking the DriveLock client or the console
  2. If running version 24.1.x, upgrade to version 24.1.6 or later
  3. If running version 24.2.x, upgrade to version 24.2.7 or later
  4. If running version 25.1.x, upgrade to version 25.1.5 or later
  5. Verify the upgrade was successful and test that privileged operations function correctly
  6. Review user permissions and ensure the privilege manipulation vector is no longer exploitable
Caveat Review release notes for your specific version path for any changes to functionality or configuration requirements

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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