CVE-2025-67792
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 · uneditedAn 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 a DriveLock process to execute arbitrary commands 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 · high confidenceA local privilege escalation vulnerability in DriveLock allows unprivileged Windows users to manipulate the DriveLock process to execute arbitrary commands. This affects versions 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5.
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>= 24.1, < 24.1.6>= 24.2, < 24.2.7>= 25.1, < 25.1.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify DriveLock is installedCheck for DriveLock installation by searching in Program Files directory, Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or using system inventory tools like SCCM or PowerShell Get-WmiObject Win32_ProductAffected if DriveLock is found on the system
-
Determine installed DriveLock versionLocate the DriveLock executable (typically named DriveLock.exe or similar in the installation directory) and check its file properties for version information, or query via Windows Installer API: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*DriveLock*'} | Select-Object Name, VersionAffected if Version cannot be determined or returns a value outside expected ranges
-
Compare version against affected rangesCompare the installed version number to these affected ranges: 24.1.x where x < 6, 24.2.x where x < 7, or 25.1.x where x < 5. Any version matching 24.1 through 24.1.5, 24.2 through 24.2.6, or 25.1 through 25.1.4 is affected.Affected if Version falls within >= 24.1 < 24.1.6, OR >= 24.2 < 24.2.7, OR >= 25.1 < 25.1.5
-
Confirm DriveLock service is runningCheck if DriveLock service or process is active by running Get-Service | Where-Object {$_.Name -like '*DriveLock*'} or Get-Process | Where-Object {$_.ProcessName -like '*DriveLock*'}Affected if DriveLock service or process is actively running on the system
A user is affected if DriveLock is installed, the installed version falls within any of the three affected ranges, and the DriveLock service or process is running on the system.
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 · scoped24.1.624.2.725.1.5
Upgrade DriveLock to version 24.1.6, 24.2.7, or 25.1.5 or later to remediate the vulnerability. As a temporary mitigation, limit local access to trusted users only.
Upgrade to DriveLock 24.1.6, 24.2.7, or 25.1.5 depending on your current major version line
- Identify the currently installed DriveLock version (24.1.x, 24.2.x, or 25.1.x)
- Back up any critical DriveLock configuration data or policies
- Download the corresponding fixed version from the official DriveLock vendor source (24.1.6 for 24.1.x, 24.2.7 for 24.2.x, or 25.1.5 for 25.1.x)
- Apply the upgrade following standard DriveLock installation procedures
- Restart the DriveLock service if required after the update
- Verify the installed version matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67792 — 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-2025-67792 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