☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
ZDI logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 🐛 CWE-22
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2026-5487

CVE-2026-5487 — DriveLock Directory Traversal Information Disclosure Vulnerability
📅 PUBLISHED: 2026-07-29 00:00 UTC 🔄 UPDATED: 2026-08-27 19:37 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 1.54%
👁️
1.54% probability
38.4× above the median CVE
Tier: HIGH
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Germany License: Commercial
VULNERABLE: Unknown
CVSS VECTOR BREAKDOWN 7.5
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: N User Interaction None
S: U Scope Unchanged
C: H Confidentiality High
I: N Integrity None
A: N Availability None
7.5
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-5487 is a directory traversal vulnerability in the DriveLock web service on TCP port 4568 that enables unauthenticated remote attackers to disclose sensitive files. It affects DriveLock installations with no authentication required and no patches available from any tracked source. The CVSS 7.5 score reflects high confidentiality impact with no integrity or availability effects.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

The flaw resides in the DriveLock web service listener on TCP port 4568. Insufficient validation of user-supplied path parameters occurs before the values are passed to file read operations. Attackers supply traversal sequences such as "../" or "..%2f" that bypass intended directory restrictions and reach arbitrary files readable by the service account. The root cause aligns with CWE-22 path traversal, where canonicalization and sanitization steps are absent prior to filesystem access. The attack surface is the unauthenticated HTTP or HTTPS endpoints exposed by default, allowing direct requests without prior session establishment. No code-level details from the vendor are public, but the mechanism follows standard path traversal patterns in web applications handling file parameters.

Exploitation Scenarios

  1. Reconnaissance identifies exposed DriveLock instances via Shodan queries for port 4568 or service banners containing "DriveLock".
  2. An attacker sends crafted HTTP requests to the web service endpoint containing a path parameter with traversal sequences, for example GET /service?file=../../../../windows/win.ini or equivalent Unix paths, targeting readable configuration or credential files.
  3. The web service processes the unsanitized path, opens the target file under the service account context, and returns its contents in the HTTP response.
  4. Post-exploitation the attacker exfiltrates disclosed data such as configuration files, logs, or application secrets to map further internal assets or escalate privileges via obtained credentials.

Impact Assessment

Affected systems include any DriveLock deployment exposing the web service on port 4568. Blast radius centers on confidentiality loss of files accessible to the service account, potentially including sensitive enterprise policy data or logs. The CVSS vector shows full network attack vector, low complexity, no privileges or user interaction required, and unchanged scope, producing a 7.5 High rating driven solely by the C:H subscore.

Detection Guidance

Sigma Rule

title: DriveLock Directory Traversal Attempt
id: 8f4c2a1b-9e3d-4f7a-8b2c-1d9e4f3a2b1c
status: experimental
description: Detects path traversal in DriveLock web service requests on port 4568
logsource:
  category: webserver
  product: DriveLock
detection:
  selection:
    c-uri-query|contains:
      - '../'
      - '..%2f'
      - '..%5c'
    c-port: 4568
  condition: selection
fields:
  - src_ip
  - c-uri
level: high

YARA Rule

rule DriveLock_Path_Traversal_Attempt {
    meta:
        description = "Detects path traversal patterns targeting DriveLock service"
        author = "valtersit.com"
        date = "2026-01-01"
    strings:
        $traversal = /[\.\.\/\\]{2,}/
        $port = "4568"
    condition:
        $traversal and $port
}

Suricata IDS Rule

alert http any any -> any 4568 (msg:"DriveLock Directory Traversal CVE-2026-5487"; flow:established,to_server; http.uri; content:"../"; nocase; sid:20265487; rev:1;)

Elastic Detection

sequence by source.ip with maxspan=5m
  [network where destination.port == 4568 and url.path like "*../*"]

Splunk SPL Query

index=web sourcetype=drive_lock_logs dest_port=4568 uri_path="*/../*" 
| stats count by src_ip uri_path 
| where count > 1

Wazuh OSSEC Rule

<rule id="430905" level="12">
  <if_sid>1002</if_sid>
  <match>DriveLock.*port 4568.*\.\./</match>
  <description>DriveLock directory traversal detected on port 4568</description>
</rule>

Mitigation & Patch Guidance

Patch confidence: 0/4 (UNPATCHED — no patch evidence from any tracked source).

  1. Immediate mitigations include network segmentation to restrict access to port 4568, deployment of WAF rules blocking traversal sequences, and monitoring for anomalous requests containing "../".
  2. Patch/upgrade steps: monitor vendor channels for future DriveLock releases addressing ZDI-CAN-28746; apply updates immediately upon release.
  3. Long-term hardening involves disabling the web service if unused, enforcing strict input validation on all path parameters, and running the service under least-privilege accounts.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-5487
https://www.zerodayinitiative.com/advisories/ZDI-CAN-28746/
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-5487
DriveLock vendor security advisories (no entries found)
No public exploit-in-the-wild evidence or threat actor campaigns identified as of report date.

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

port:4568
DriveLock
http.title:DriveLock
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-5487/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.