dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-5942

MEDIUM · 5.7 CVSS v4.0 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Netskope was notified about a potential gap in its agent (NS Client) on Windows systems. If this gap is successfully exploited, an unprivileged user can trigger a heap overflow in the epdlpdrv.sys driver, leading to a Blue-Screen-of-Death (BSOD). Successful exploitation can also potentially be performed by an unprivileged user whose NS Client is configured to use Endpoint DLP. A successful exploit can result in a denial-of-service for the local machine.

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 · moderate confidence

A heap overflow vulnerability exists in the epdlpdrv.sys kernel driver of Netskope's NS Client on Windows systems. When Endpoint DLP is enabled, an unprivileged local user can trigger the overflow, causing a Blue Screen of Death and resulting in local denial of service.

MitigationApply the vendor-supplied patch or updated version of Netskope NS Client once released. As a temporary measure, evaluate whether Endpoint DLP functionality can be disabled if the patch is not immediately available.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Netskope NS Client is installed
    Look for the Netskope client installation directory, typically at C:\Program Files\Netskope\ or C:\Program Files (x86)\Netskope\, and confirm the presence of Netskope client executables.
    Affected if Netskope NS Client software is installed on the system.
  2. Confirm epdlpdrv.sys driver exists
    Search for epdlpdrv.sys file in the Netskope installation directory or subdirectories (e.g., C:\Program Files\Netskope\Drivers\ or C:\Windows\System32\drivers\). Use PowerShell: Get-ChildItem -Path 'C:\Program Files\Netskope' -Recurse -Filter 'epdlpdrv.sys' -ErrorAction SilentlyContinue.
    Affected if The epdlpdrv.sys driver file is present on the system.
  3. Check if the vulnerable driver is loaded
    Open an elevated PowerShell or Command Prompt and run: sc query epdlpdrv or driverquery /v | findstr epdlpdrv to check if the driver is currently running.
    Affected if The epdlpdrv driver service state shows as RUNNING.
  4. Determine if Endpoint DLP is enabled
    Check Netskope client configuration or registry for DLP policy status. Look in HKLM\SOFTWARE\Netskope\ or HKCU\SOFTWARE\Netskope\ for EndpointDLP or DLPEnabled registry keys. Alternatively, check the Netskope client UI for Endpoint DLP status if accessible.
    Affected if Endpoint DLP functionality is enabled in the Netskope client configuration.
  5. Check driver version for patch status
    Right-click epdlpdrv.sys, select Properties, then view the Details tab for File Version and Product Version. Compare against any vendor-released patch versions when available.
    Affected if The driver version does not reflect the patched version once released by Netskope.

The system is affected if Netskope NS Client is installed with the epdlpdrv.sys driver present, Endpoint DLP is enabled, and the driver has not been updated to the patched version.

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

Apply the vendor-supplied patch or updated version of Netskope NS Client once released. As a temporary measure, evaluate whether Endpoint DLP functionality can be disabled if the patch is not immediately available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5942 — 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-5942 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