Netskope Client vulnerabilities
5 known vulnerabilities in Netskope Client from Netskope. 5 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.0 High severity
Netskope Client: Improper Validation of Integrity Check Value
Netskope has identified a potential gap in its agent (Netskope Client) in which a malicious insider can potentially tamper the Netskope Client configuration by performing MITM (Man-in-the-Middle) activity on the Netskope Client communication channel. A success
- 7.5 High severity
Netskope Client: Improper Authentication
Netskope was notified about a security gap in Netskope Client enrollment process where NSClient is using a static token “Orgkey” as authentication parameter. Since this is a static token, if leaked, cannot be rotated or revoked. A malicious actor can use this
- 8.8 High severity
Netskope Client: Improper Preservation of Permissions
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 whe
- 7.0 High severity
Netskope Client: Time-of-check Time-of-use (TOCTOU) Race Condition
The Netskope client service (prior to R96) on Windows runs as NT AUTHORITY\SYSTEM which writes log files to a writable directory (C:\Users\Public\netSkope) for a standard user. The files are created and written with a SYSTEM account except one file (logplaceho
- 7.8 High severity
Netskope Client: Improper Limitation of a Pathname to a Restricted Directory
The Netskope client service running with NT\SYSTEM privileges accepts network connections from localhost to start various services and execute commands. The connection handling function of Netskope client before R100 in this service utilized a relative path to