Skip to main content

DriveLock EUVDEUVD-2026-50492

| CVE-2026-5487 HIGH
Path Traversal (CWE-22)
2026-07-29 zdi GHSA-4m2w-557x-2rqf
7.5
CVSS 3.0 · Vendor: zdi
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach DriveLock web service on port 4568
  2. Delivery
    Send crafted request with traversal path
  3. Exploit
    Bypass missing path validation
  4. Execution
    Read arbitrary file as service account
  5. Impact
    Exfiltrate sensitive information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the DriveLock web service on TCP port 4568 (its default listening port); no authentication, credentials, or user interaction are needed (PR:N/UI:N). The primary limiting factor is exposure of that port - installations where port 4568 is firewalled off from untrusted networks are not remotely reachable - and the read is bounded by the privileges of the service account, so only files that account can access are disclosable. No non-default configuration is required beyond the web service being enabled and reachable.

Impact

All available signals point to a genuine, easily exploitable disclosure issue rather than a high-CVSS-but-low-real-risk case. The CVSS 3.0 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) indicates a network-reachable, low-complexity, unauthenticated attack with no user interaction and high confidentiality impact but no integrity or availability effect - consistent with arbitrary file read. No EPSS score, KEV entry, SSVC decision, or POC was provided in the input, so real-world exploitation probability cannot be quantified from this data; the absence of a POC and KEV listing suggests it is not yet known to be exploited at scale. The main factor tempering priority is deployment footprint: DriveLock is a niche endpoint-security product, so exposure depends on how many installations expose port 4568 to untrusted networks. Priority should be HIGH for any organization running DriveLock with the web service reachable from untrusted segments, given trivial exploitability and sensitive-data exposure.

Exploit ScenarioDerived

An attacker with network reach to the DriveLock host sends a crafted HTTP request to the web service on TCP port 4568 containing a path parameter with directory-traversal sequences (e.g. ../../). Because the path is not validated, the service reads and returns a file outside the intended directory - such as configuration files, credentials, or logs - all without authentication. No public exploit is identified at time of analysis, but the low complexity makes weaponization straightforward.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 1.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 29, 2026

Unauthenticated information disclosure in DriveLock's web service (default TCP port 4568) lets remote attackers read arbitrary files via directory traversal, exposing sensitive data in the context of the service account. The flaw stems from missing validation of a user-supplied path before it is used in file operations (CWE-22). Discovered and reported through the Zero Day Initiative (ZDI-26-284 / ZDI-CAN-28746); no public exploit identified at time of analysis, and it is not listed in CISA KEV.

RemediationAI

Apply the fix described in DriveLock Security Bulletin 26-003 (https://www.drivelock.help/sb/Content/SecurityBulletins/26-003-PathValidation.htm); patch available per vendor advisory, though an exact fixed version number is not stated in the provided data, so confirm the target build directly with the bulletin before upgrading. As a compensating control until patched, restrict network access to TCP port 4568 using host or network firewall rules so that only trusted management hosts can reach the web service - this closes the remote attack surface but may break legitimate management or agent communication that relies on that port, so validate connectivity after applying. Where feasible, place the DriveLock web service behind a reverse proxy or VPN and remove any direct exposure to untrusted or internet-facing networks. Also review service-account permissions to limit what files the account (and therefore a successful traversal) can read, and monitor the service logs for anomalous path parameters containing traversal sequences.

Affected VersionsENISA

DriveLock 25.2.2.61370

Affected Packages

euvd drivelock no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

DriveLock is an enterprise endpoint-security / device-control and application-control suite whose management components expose an HTTP-based web service listening on TCP port 4568 by default. The vulnerability is a classic CWE-22 path traversal (relative/absolute path abuse) in which the service accepts a client-supplied path parameter and passes it into a file-read operation without canonicalizing or constraining it to an intended base directory. Because traversal sequences (e.g. ../) are not stripped or rejected, an attacker can escape the intended directory and read files anywhere the service account can access. Per the CPE (cpe:2.3:a:drivelock:drivelock:*:*:*:*:*:*:*:*), the affected component is the DriveLock application itself rather than an OS or third-party library.

Know when Drivelock gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (zdi) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network-reachable arbitrary file read on default port 4568 gives AV:N/AC:L/PR:N/UI:N with C:H and no integrity or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (zdi).

CVSS VectorVendor: zdi

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

DriveLock Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of DriveLock. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the web service, which listens on TCP port 4568 by default. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-28746.

Executive ViewAI

Why It Matters

DriveLock's web service contains an unauthenticated remote file disclosure vulnerability (CVE-2026-5487, CVSS 7.5) allowing attackers without credentials to read arbitrary files from any internet-connected instance. Organizations running DriveLock face immediate risk of data breach through exposure of files accessible to the service account, including credentials and sensitive business data.

Business Impact: High
Compensating Controls

Restrict network access to DriveLock's TCP port 4568 to internal trusted networks only; disable the web service interface if not required for operational needs; implement file integrity monitoring and access logging on sensitive data directories; isolate DriveLock systems within a network segment to limit data exposure in the event of compromise; maintain offline backups of critical files to mitigate breach impact.

Threat Intelligence Overview

EPSS Score
1.5%
Top 28% exploitable
Prevalence
Low
niche enterprise endpoint-security vendor, limited global deployment footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 1.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: +2
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2025-67781 CRITICAL
9.9 Dec 17

Local privilege escalation in the DriveLock Windows endpoint agent (24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 bef

CVE-2025-67791 CRITICAL
9.8 Dec 17

DriveLock tenants whose agent-authentication configuration is incomplete can be attacked by unauthenticated remote actor

CVE-2025-67793 CRITICAL
9.8 Dec 17

Privilege escalation in DriveLock allows an authenticated user who holds the 'Manage roles and permissions' privilege to

CVE-2025-67787 CRITICAL
9.6 Dec 17

Cross-site scripting in the DriveLock Operations Center web console (versions 25.1.2 through 25.1.4) lets an attacker in

CVE-2026-5490 HIGH
8.8 Jul 29

Privilege escalation in DriveLock via SQL injection lets authenticated remote attackers reach resources normally protect

CVE-2026-5491 HIGH
7.5 Jul 29

Unauthenticated directory traversal in the DriveLock endpoint-security agent's web service (TCP 6067 by default) lets re

CVE-2025-67792 HIGH
7.8 Dec 17

Local privilege escalation in DriveLock endpoint-security agents (24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 befor

CVE-2025-67790 HIGH
7.5 Dec 17

Unprivileged local users on Windows hosts running affected DriveLock builds (24.1 before 24.1.6, 24.2 before 24.2.7, and

CVE-2026-5492 MEDIUM
6.5 Jul 29

Path traversal in DriveLock's built-in web service exposes arbitrary files readable by the service account to any authen

CVE-2025-67794 MEDIUM
6.1 Dec 17

Incorrect permission assignments on directories and files created by the DriveLock endpoint agent let any local non-admi

CVE-2026-5489 MEDIUM
5.3 Jul 29

Directory traversal in DriveLock's built-in web service (TCP port 4568) permits unauthenticated remote attackers to read

CVE-2025-67789 MEDIUM
5.3 Dec 17

Cross-tenant information disclosure in DriveLock 24.1 (before 24.1.6), 24.2 (before 24.2.7), and 25.1 (before 25.1.5) al

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy