DriveLock up to 24.1.x/24.2.x/25.1.5 API Call permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in DriveLock up to 24.1.x/24.2.x/25.1.5. Affected is an unknown function of the component API Call Handler. The manipulation leads to permission. This vulnerability is documented as CVE-2025-67793. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in DriveLock up to 24.1.x/24.2.x/25.1.5. This issue affects an unknown code of the component API Call Handler. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at drivelock.help. The identification of this vulnerability is CVE-2025-67793 since 12/12/2025. The exploitation is known to be easy. The exploitation needs additional levels of successful authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Upgrading to version 25.1.6 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2879). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- DriveLock DriveLock
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: DriveLock 25.1.6
Timeline
12/12/2025 CVE reserved12/17/2025 Advisory disclosed
12/17/2025 VulDB entry created
12/18/2025 VulDB entry last update
Sources
Advisory: drivelock.helpStatus: Confirmed
CVE: CVE-2025-67793 (🔒)
GCVE (CVE): GCVE-0-2025-67793
GCVE (VulDB): GCVE-100-337061
CERT Bund: WID-SEC-2025-2879 - DriveLock: Mehrere Schwachstellen
Entry
Created: 12/17/2025 22:20Updated: 12/18/2025 20:07
Changes: 12/17/2025 22:20 (54), 12/18/2025 20:07 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.