CVE-2019-10882
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 · uneditedThe Netskope client service, v57 before 57.2.0.219 and v60 before 60.2.0.214, running with NT\SYSTEM privilege, accepts network connections from localhost. The connection handling function in this service suffers from a stack based buffer overflow in "doHandshakefromServer" function. Local users can use this vulnerability to trigger a crash of the service and potentially cause additional impact on the system.
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 confidenceThe Netskope client service running as NT\SYSTEM privilege contains a stack-based buffer overflow in the 'doHandshakefromServer' function. The service accepts network connections from localhost without proper validation, allowing local users to trigger a buffer overflow that can crash the service or potentially execute arbitrary code with SYSTEM privileges.
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>= 57, < 57.2.0.219>= 60, < 60.2.0.214CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Netskope Client is installedCheck for the Netskope service by running 'sc query Netskope' or look for the installation in Program Files (typically C:\Program Files\Netskope)Affected if The Netskope service or installation directory exists on the system
-
Retrieve the installed Netskope versionCheck the version by looking at the executable properties (ntnxsvc.exe in the Netskope installation folder), or query the registry under HKLM\SOFTWARE\Netskope or HKLM\SOFTWARE\WOW6432Node\Netskope for the version valueAffected if The installed version falls within the affected ranges: v57.x before 57.2.0.219, or v60.x before 60.2.0.214
-
Confirm the Netskope service is runningRun 'sc query Netskope' or check via Services snap-in (services.msc) to see if the Netskope service is in a running stateAffected if The service is running and listening for connections
-
Verify the service runs as SYSTEM privilegeRun 'sc qc Netskope' to view the service configuration, or use Task Manager to view the service's logged-on userAffected if The service is configured to run as NT AUTHORITY\SYSTEM or LocalSystem
The system is affected if Netskope Client is installed with version 57.x before 57.2.0.219 or version 60.x before 60.2.0.214, and the service is running with SYSTEM privileges.
Generated from the published advisory. Verify against your own configuration.
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 data57.2.0.21960.2.0.214
Upgrade Netskope client to version 57.2.0.219 or later (for v57) or version 60.2.0.214 or later (for v60). This vulnerability is exploitable by local users, so restrict local access to trusted personnel until patched.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10882 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10882 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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