Drivelock: Improper Privilege Management
CVE-2025-67793 is a critical-severity improper privilege management vulnerability in Drivelock, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 25.1.6 as the first without the flaw, so updating Drivelock to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.32% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Drivelock to 25.1.6 or a later version.
- Read the advisory on drivelock.help for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Drivelock | Drivelock | 24.1 through 24.1.6; 24.2 through 24.2.8; 25.1 up to, but not including, 25.1.6 | 25.1.6 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
An issue was discovered in DriveLock 24.1 through 24.1.*, 24.2 through 24.2.*, and 25.1 before 25.1.6. Users with the "Manage roles and permissions" privilege can promote themselves or other DOC users to the Supervisor role through an API call. This privilege is included by default in the Administrator role. This issue mainly affects cloud multi-tenant deployments; on-prem single-tenant installations are typically not impacted because local admins usually already have Supervisor privileges.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Drivelock
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.5 High severity
Recent Improper Privilege Management vulnerabilities
- 8.8 High severity
- 9.9 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.