No analysis available yet.
Vendor Solution
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/
Vendor Workaround
There is no countermeasure available to remediate the gap without enabling Secure Enrollment, but follow the below steps to minimize the risk: * Enable device compliance and device classification * Create a policy to block all traffic for the devices which are not meeting the device compliance checks and are not falling under proper device classification.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-48332 | 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. |
Wed, 23 Jul 2025 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
cvssV4_0
|
cvssV4_0
|
Thu, 05 Sep 2024 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Netskope
Netskope netskope |
|
| CPEs | cpe:2.3:a:netskope:netskope:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Netskope
Netskope netskope |
|
| Metrics |
cvssV3_1
|
Wed, 28 Aug 2024 06:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 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. | 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. |
Mon, 26 Aug 2024 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 26 Aug 2024 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 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. | |
| Title | Client Enrollment Process Bypass | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: Netskope
Published:
Updated: 2025-07-23T11:02:11.214Z
Reserved: 2024-08-02T07:20:21.411Z
Link: CVE-2024-7401
Updated: 2024-08-26T17:34:39.297Z
Status : Modified
Published: 2024-08-26T17:15:06.987
Modified: 2025-07-23T11:15:32.100
Link: CVE-2024-7401
No data.
OpenCVE Enrichment
No data.
EUVD