NetskopeApplication

CVE-2023-4996

HIGH · 8.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 101 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 its NSClient product for version 100 & prior where a malicious non-admin user can disable the Netskope client by using a specially-crafted package. The root cause of the problem was a user control code when called by a Windows ServiceController did not validate the permissions associated with the user before executing the user control code. This user control code had permissions to terminate the NSClient service. 

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 vulnerability in Netskope NSClient (version 100 and prior) allows a malicious non-admin user to terminate the NSClient service via a specially-crafted package. The root cause is a Windows ServiceController user control code path that fails to validate user permissions before executing service control operations, granting unprivileged users the ability to stop the client service.

MitigationUpgrade Netskope NSClient to a version newer than 100 (or apply vendor-supplied patches) which includes proper permission validation before allowing service control operations. Until patched, restrict user access to prevent unprivileged users from manipulating Windows services.

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
NetskopeApplication
Affected:< 101

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Check installed Netskope NSClient version
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Netskope\NSClient or check Add/Remove Programs for Netskope NSClient version
    Affected if Version is 100 or lower (versions prior to 101 are affected)
  2. Verify NSClient Windows service exists
    Open Services console (services.msc) and locate the 'Netskope NSClient' service, or run: sc query NSClient
    Affected if The service exists and is running on the system
  3. Check service permissions configuration
    Run: sc sdshow NSClient (displays the Security Descriptor Definition Language) or check via PowerShell Get-Service -Name NSClient | Get-Sddl
    Affected if Non-admin users have SERVICE_STOP or SERVICE_CONTROL permissions (look for (A;;CCDCSW;;;BU) or similar allowing built-in users group)
  4. Identify non-admin users on the system
    Run 'net user' or check Local Users and Groups (lusrmgr.msc) to enumerate user accounts with access to the system
    Affected if There are non-admin user accounts present on the system

A system is affected if Netskope NSClient version 100 or prior is installed AND non-admin users exist who could exploit the ServiceController permission gap to stop the service.

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
Upgrade available Upgrade to 101 or later
Fixed in 101
Interim mitigation

Upgrade Netskope NSClient to a version newer than 100 (or apply vendor-supplied patches) which includes proper permission validation before allowing service control operations. Until patched, restrict user access to prevent unprivileged users from manipulating Windows services.

Recommended fix Moderate confidence

Version 101

  1. Upgrade Netskope NSClient to version 101 or later to resolve the permission validation vulnerability
  2. Verify the upgrade by confirming the NSClient service remains active and cannot be terminated by non-admin users

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

Fix this in Netskope Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-4996 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