DriveLock vulnerabilities

In DriveLock versions 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).

In DriveLock versions 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.

In DriveLock versions 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.

A Directory Traversal vulnerability in DriveLock allows a remote, authenticated attacker to read sensitive files. The issue is in the web service listening on TCP port 4568, which does not properly validate user-supplied paths.

DriveLock has a directory traversal vulnerability in its web service on port 6067, allowing an unauthenticated remote attacker to disclose sensitive information due to lack of path validation.

DriveLock has an SQL injection vulnerability in its web service on port 4568, allowing an authenticated remote attacker to escalate privileges due to lack of input validation in SQL queries.

A Directory Traversal vulnerability in DriveLock allows a remote, unauthenticated attacker to read sensitive files. The issue is in the web service listening on TCP port 4568, which does not properly validate user-supplied paths.

DriveLock has a directory traversal vulnerability in its web service on port 4568, allowing an unauthenticated remote attacker to disclose sensitive information due to lack of path validation.