dbcve.org
DrivelockApplication

CVE-2025-67791

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to after 25.1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 through 24.2.*, and 25.1 through 25.1.*. An incomplete configuration (agent authentication) in DriveLock tenant allows attackers to impersonate any DriveLock agent on the network against the DES (DriveLock Enterprise Service).

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

An incomplete agent authentication configuration in DriveLock tenant management allows remote network attackers to impersonate any DriveLock agent when communicating with the DriveLock Enterprise Service (DES), enabling unauthorized access to the centralized management infrastructure.

MitigationProperly configure agent authentication in the DriveLock tenant, ensuring certificates or credentials are correctly established for all agents before allowing network communication with the DES.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Check installed DriveLock version
    Locate the DriveLock installation and retrieve its version number (typically via the product UI, registry, or installed programs list). Compare the version to the affected ranges: 24.1 through 24.1.4, 24.2 through 24.2.8, or 25.1 through 25.1.6.
    Affected if The installed version falls within any of the affected ranges.
  2. Access DriveLock tenant management configuration
    Log into the DriveLock Management Console and navigate to the tenant management section where agent authentication settings are defined. Look for the agent-to-DES authentication configuration area.
    Affected if The tenant management interface is accessible and agent authentication settings can be viewed or modified.
  3. Verify agent certificate or credential configuration
    In the tenant management configuration, inspect the agent authentication settings. Check whether valid certificates or credentials have been established for agents communicating with the DriveLock Enterprise Service (DES). Look for indicators such as certificate status, credential validity, or authentication method configuration.
    Affected if No certificates or credentials are configured, or the configuration shows incomplete or missing agent authentication for DES communication.
  4. Confirm DES network exposure
    Determine if the DriveLock Enterprise Service is accessible over the network from untrusted locations. This may involve reviewing firewall rules, network segmentation, or DES binding configuration.
    Affected if The DES is reachable from remote/network locations without proper network segmentation or access controls.

A user is affected if their DriveLock version is within the affected ranges AND agent authentication (certificates or credentials) is not properly configured in the tenant settings, particularly if the DES is network-accessible.

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.

From vendor data
Upgrade available Upgrade to a release after 25.1.6
Interim mitigation

Properly configure agent authentication in the DriveLock tenant, ensuring certificates or credentials are correctly established for all agents before allowing network communication with the DES.

Fix this in Drivelock Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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