Bug fixes
DriveLock 2025.2 Patch 2 is a patch version.
This chapter contains information on errors that have been fixed with DriveLock version 2025.2 Patch 2. Our External Issues (EI) numbers, if available, serve as a reference.
| Application Control | |
|---|---|
|
EI-3158 |
An issue has been fixed where modifications to nested filters in application control rules were not retained when saving the main rule. |
| DriveLock Enterprise Service (DES) | |
|---|---|
|
EI-3142 |
An error in the DLSetup.exe has been fixed, which caused the DES installation to abort under certain circumstances. |
|
DriveLock On-Premise only: Fixed a security issue that allowed unauthorized users to access DES configuration data via URL manipulation. |
|
|
A vulnerability has been fixed that allowed SQL code to be injected under certain circumstances. |
|
|
A vulnerability in user path validation in the DriveLock Enterprise Service (DES) has been resolved that could allow remote attackers to access files outside the intended directory structure. |
|
|
A potential crash in the DES during log file initialization has been fixed. |
| DriveLock Operations Center (DOC) | |
|---|---|
|
An issue has been fixed where users without the role permission “Manage policy settings” were unable to add devices or drives to rules in the DOC. |
|
|
An issue has been fixed where the “Date created” and “Date modified” columns remained empty when a large number of rules were displayed. |
|
|
EI-3148 |
Unlock requests in the DOC could only be processed if the role permission “Manage drives, devices, or applications in rules from the DOC” was assigned. This permission is now only required for “Create new rule”; adding to existing rules is possible without this permission. |
|
An issue has been fixed that prevented the creation of application rules for Linux. |
|
Reference |
Encryption 2-Go |
|---|---|
|
EI-3146 |
An issue has been fixed where creating a container on an exFAT-formatted USB drive took longer than expected. |
| Inventory | |
|---|---|
|
EI-3127 |
An issue has been fixed where users in the DOC were not assigned to the correct Active Directory structure and an incorrect value was displayed in the Domain column. |
| Vulnerability Scan | |
|---|---|
|
An error when synchronizing CVE entries has been fixed. |