CVE-2019-12091
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 command injection vulnerability. Local users can use this vulnerability to execute code with NT\SYSTEM privilege.
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 versions prior to 57.2.0.219 and 60.2.0.214 run with NT\SYSTEM privileges and accept localhost network connections. A command injection vulnerability exists in the connection handling function, allowing local authenticated users to inject and execute arbitrary commands with SYSTEM-level 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.
-
Identify if Netskope client is installedCheck for the presence of Netskope client software on the system. Look for installation directories such as C:\Program Files\Netskope\ or check Add/Remove Programs for Netskope entries.Affected if Netskope client is found installed on the system.
-
Determine installed Netskope client versionLocate the Netskope client version information. Check the executable version details, typically found in the Netskope client installation folder (e.g., NTProxy.exe or NetskopeClient.exe), or query the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Netskope entries.Affected if The installed version number cannot be determined or is found within the vulnerable ranges.
-
Verify version falls within affected rangesCompare the installed version against the affected ranges: version 57.x before 57.2.0.219, or version 60.x before 60.2.0.214. Note that versions below 57 are not affected by this specific CVE.Affected if The installed version is >= 57 and < 57.2.0.219, OR >= 60 and < 60.2.0.214.
-
Confirm Netskope service is runningCheck if the Netskope client service (typically named 'Netskope TA' or 'Netskope Client') is currently running on the system using Task Manager or the 'sc query' command.Affected if The Netskope service is running and the version is within the affected ranges.
A system is affected if the Netskope client is installed with a version between 57.0.0.0 and 57.2.0.218, or between 60.0.0.0 and 60.2.0.213, and the service is actively running.
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, or 60.2.0.214 or later. If immediate patching is not feasible, consider network-based restrictions on the service or disable the service if not required for business operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12091 — 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-12091 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