dbcve.org
NetdriveApplication · Bdrive

CVE-2025-2768

HIGH · 7.8 CVSS v3.0 Published 2025-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bdrive NetDrive Uncontrolled Search Path Element Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Bdrive NetDrive. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the configuration of OpenSSL. The product loads an OpenSSL configuration file from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-25041.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a local privilege escalation vulnerability in Bdrive NetDrive caused by an uncontrolled search path element. The application loads an OpenSSL configuration file from an unsecured location, allowing a local attacker who already has low-privileged code execution to place a malicious config file in the search path and escalate to SYSTEM privileges.

MitigationRemediate by securing the OpenSSL configuration file loading mechanism to use absolute, trusted paths and ensuring the configuration directory has restricted permissions to prevent injection of malicious configuration files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NetdriveApplication
Affected:= 3.17.960

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Bdrive NetDrive installation
    Check for the presence of Bdrive NetDrive by searching for the application in typical installation locations such as C:\Program Files\Bdrive\NetDrive or C:\Program Files (x86)\Bdrive\NetDrive, or by using 'Get-ItemProperty' in PowerShell against registry keys HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\* and HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* for entries containing 'NetDrive' or 'Bdrive'.
    Affected if Bdrive NetDrive is found on the system.
  2. Identify installed version
    Locate the NetDrive executable (typically NetDrive.exe in the installation directory) and run 'Get-ItemProperty -Path "C:\Program Files\Bdrive\NetDrive\NetDrive.exe" | Select-Object VersionInfo' or right-click the executable, select Properties, and view the File Version on the Details tab.
    Affected if The version displayed is 3.17.960.
  3. Locate OpenSSL configuration files
    Search for openssl.cnf or openssl.cfg files within the NetDrive installation directory and parent directories. Use PowerShell: 'Get-ChildItem -Path "C:\Program Files\Bdrive" -Recurse -Filter "openssl*.cnf" -ErrorAction SilentlyContinue | Select-Object FullName'. Also check the current working directory from which NetDrive is launched and the application directory.
    Affected if OpenSSL configuration files exist in the NetDrive installation folder or directories accessible to low-privileged users.
  4. Inspect directory permissions
    Right-click the directories containing the OpenSSL config files (such as the NetDrive installation folder), select Properties, go to the Security tab, and verify which users and groups have Write or Modify permissions. Alternatively, use 'Get-Acl "C:\Program Files\Bdrive\NetDrive" | Select-Object -ExpandProperty Access' in PowerShell.
    Affected if Users with low-privileged accounts (such as standard users orAuthenticated Users) have Write or Modify access to directories containing OpenSSL configuration files.

A system is affected if Bdrive NetDrive version 3.17.960 is installed and low-privileged users can write to directories where the application searches for or stores OpenSSL configuration files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remediate by securing the OpenSSL configuration file loading mechanism to use absolute, trusted paths and ensuring the configuration directory has restricted permissions to prevent injection of malicious configuration files.

Fix this in Netdrive Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2768 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2768 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data