First published: Mon Aug 26 2024(Updated: )
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 token to enroll NSClient from a customer’s tenant and impersonate a user.
Credit: psirt@netskope.com
Affected Software | Affected Version | How to fix |
---|---|---|
Netskope |
Netskope has fixed the gap and recommends customers to review their deployments of Netskope Client and enable the fix in their tenants. Here is the detailed guide - https://docs.netskope.com/en/secure-enrollment/
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-7401 is considered a critical vulnerability due to the use of a static authentication token that cannot be rotated or revoked.
To fix CVE-2024-7401, organizations should update their Netskope Client to the latest version that addresses this vulnerability.
CVE-2024-7401 allows an attacker to potentially gain unauthorized access to the Netskope Client by exploiting the static token during enrollment.
As of now, there are reports suggesting that CVE-2024-7401 is being actively exploited in the wild.
If you suspect exposure due to CVE-2024-7401, you should immediately revoke all potentially compromised tokens and update to a patched version of the Netskope Client.