CVE-2024-8535
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 · uneditedAuthenticated user can access unintended user capabilities in NetScaler ADC and NetScaler Gateway if the appliance must be configured as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) with KCDAccount configuration for Kerberos SSO to access backend resources OR the appliance must be configured as an Auth Server (AAA Vserver) with KCDAccount configuration for Kerberos SSO to access backend resources
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 · moderate confidenceAuthenticated users can access unintended user capabilities in NetScaler ADC and NetScaler Gateway when the appliance is configured as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) OR as an Auth Server (AAA Vserver), in both cases with KCDAccount configuration for Kerberos SSO. This represents an authorization bypass where users may gain access to privileges or capabilities beyond their assigned role.
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>= 12.1, < 12.1-55.321>= 12.1, < 13.1-55.34>= 13.1, < 13.1-37.207>= 14.1, < 14.1-29.72>= 12.1, < 13.1-55.34>= 14.1, < 14.1-29.72CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Check NetScaler ADC or Gateway versionRun command 'show version' or 'nsversion' from the NetScaler CLI to retrieve the installed firmware versionAffected if The installed version falls outside the patched ranges: < 12.1-55.321, < 13.1-55.34, < 13.1-37.207, or < 14.1-29.72
-
Verify if Gateway is configuredRun 'show vpn vserver' to list all VPN virtual servers. Check for SSL VPN, ICA Proxy, CVPN, or RDP Proxy configurationsAffected if Any Gateway virtual server (SSL VPN, ICA Proxy, CVPN, RDP Proxy) is configured and active
-
Verify if AAA Vserver is configured for authenticationRun 'show aaa vserver' to list all AAA virtual servers used for authenticationAffected if Any AAA authentication virtual server is configured and active
-
Check for KCDAccount configurationRun 'show kcdaccount' or 'show run | grep kcd' to identify any Kerberos Constrained Delegation accounts configured on the applianceAffected if One or more KCDAccount entries exist, indicating Kerberos SSO is configured
-
Confirm Gateway or AAA with KCDAccount overlapCross-reference the outputs from steps 2, 3, and 4. Verify that either a Gateway vserver or AAA vserver is using a KCDAccount for Kerberos SSOAffected if A Gateway virtual server OR AAA vserver is paired with a KCDAccount configuration
The environment is affected if the NetScaler runs a vulnerable version AND has a Gateway (SSL VPN/ICA Proxy/CVPN/RDP Proxy) OR an AAA Vserver configured with KCDAccount for Kerberos SSO.
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.
dbcve · scoped12.1-55.32113.1-37.20713.1-55.34
Review and restrict KCDAccount configurations on Gateway and AAA Vserver settings; audit user role assignments and permissions; apply Citrix-provided patches when released.
Upgrade to NetScaler 12.1-55.321+, 13.1-55.34+ (or 13.1-37.207+), or 14.1-29.72+ depending on your release train
- 1. Identify the currently installed NetScaler ADC or NetScaler Gateway version using 'show version' or 'nsversion' command
- 2. Determine which release train (12.1, 13.1, or 14.1) your current version belongs to
- 3. For 12.1 releases: upgrade to version 12.1-55.321 or later
- 4. For 13.1 releases: upgrade to version 13.1-55.34 or later (or 13.1-37.207 if on the 13.1-37 branch)
- 5. For 14.1 releases: upgrade to version 14.1-29.72 or later
- 6. Download the appropriate build from Citrix Downloads (download.citrix.com)
- 7. Upload the firmware to the NetScaler using the Web GUI (System > Firmware) or CLI (install firmware)
- 8. Reboot the appliance after upgrade using 'reboot' command
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.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 $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8535 — 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-2024-8535 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