dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-11616

MEDIUM · 5.6 CVSS v4.0 Published 2024-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/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 made aware of a security vulnerability in Netskope Endpoint DLP’s Content Control Driver where a double-fetch issue leads to heap overflow. The vulnerability arises from the fact that the NumberOfBytes argument to ExAllocatePoolWithTag, and the Length argument for RtlCopyMemory, both independently dereference their value from the user supplied input buffer inside the EpdlpSetUsbAction function, known as a double-fetch. If this length value grows to a higher value in between these two calls, it will result in the RtlCopyMemory call copying user-supplied memory contents outside the range of the allocated buffer, resulting in a heap overflow. A malicious attacker will need admin privileges to exploit the issue. This issue affects Endpoint DLP version below R119.

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

A double-fetch vulnerability in Netskope Endpoint DLP's Content Control Driver allows a privileged attacker to trigger a heap overflow. The EpdlpSetUsbAction function reads a length value from user-supplied input twice - once for ExAllocatePoolWithTag and once for RtlCopyMemory - without validation between calls. If the length value increases between these calls, RtlCopyMemory copies beyond the allocated buffer, causing heap overflow.

MitigationUpgrade Endpoint DLP to version R119 or later to receive the patch for this vulnerability.

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

CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:L/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 Endpoint DLP is installed
    Check for Endpoint DLP installation via program files directory, Windows registry under HKLM\SOFTWARE\Netskope, or running services (sc query for netskope related services)
    Affected if Netskope Endpoint DLP is not found on the system, the vulnerability does not apply
  2. Identify installed Endpoint DLP version
    Check registry key HKLM\SOFTWARE\Netskope\EndpointAgent\Version or look at the DLL file version of the Content Control Driver (typically epdlp.sys or similar in the install directory)
    Affected if The installed version cannot be determined or is older than the patched release; user must compare against vendor's affected version list
  3. Confirm Content Control Driver is loaded
    Run 'sc query epdlp' or check Device Manager for the Netskope DLP driver device; also verify the driver binary exists in the installation path
    Affected if The Content Control Driver (epdlp.sys) is present and loaded, the vulnerable EpdlpSetUsbAction code path exists in memory
  4. Check driver signing status
    Verify the driver is signed using 'signtool verify /v /d "Netskope Content Control Driver" <driver-path>' or via Driver Signature Enforcement status
    Affected if Driver is loaded and running, the double-fetch condition in kernel mode is reachable by a privileged attacker

The system is affected if Netskope Endpoint DLP with the Content Control Driver is installed and the installed version predates the patched release (compare against vendor's version documentation for CVE-2024-11616).

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Endpoint DLP to version R119 or later to receive the patch for this vulnerability.

Recommended fix High confidence

Endpoint DLP R119 or later

  1. Upgrade Netskope Endpoint DLP to version R119 or later to resolve the double-fetch vulnerability in the Content Control Driver

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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