CVE-2024-8534
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 · uneditedMemory safety vulnerability leading to memory corruption and Denial of Service in NetScaler ADC and Gateway if the appliance must be configured as a Gateway (VPN Vserver) with RDP Feature enabled OR the appliance must be configured as a Gateway (VPN Vserver) and RDP Proxy Server Profile is created and set to Gateway (VPN Vserver) OR the appliance must be configured as a Auth Server (AAA Vserver) with RDP Feature enabled
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 confidenceMemory safety vulnerability in NetScaler ADC and Gateway allows memory corruption leading to denial of service when specific RDP-related configurations are enabled: either a Gateway (VPN Vserver) with RDP Feature enabled, a Gateway with RDP Proxy Server Profile bound to it, or an Auth Server (AAA Vserver) with RDP Feature enabled.
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.
-
Identify NetScaler ADC versionRun command: show version or nsversionAffected if Version is 12.1 before 12.1-55.321, or 13.1 before 13.1-55.34/13.1-37.207, or 14.1 before 14.1-29.72
-
Identify NetScaler Gateway versionRun command: show version or nsversion (if Gateway is deployed as a separate instance)Affected if Version is 12.1 before 13.1-55.34, or 14.1 before 14.1-29.72
-
Check Gateway VPN vservers for RDP FeatureRun: show vpn vserver - output shows RDPStatus or RDPEnabled field under each vserver. Look for Gateway vservers with RDP feature activeAffected if Any Gateway (VPN Vserver) has RDP feature enabled
-
Check Gateway vservers for bound RDP Proxy Server ProfilesRun: show rdpprofile to list profiles, then for each Gateway vserver run: show vpn vserver <name> and check RDPProxyProfile bindingAffected if Any Gateway vserver has an RDP Proxy Server Profile bound to it
-
Check AAA vservers for RDP FeatureRun: show aaa vserver - examine each AAA Vserver for RDP-related settings such as RDPEnabled or RDPStatusAffected if Any Auth Server (AAA Vserver) has RDP feature enabled
Environment is affected if running an unpatched version AND any Gateway VPN vserver has RDP enabled, any Gateway has an RDP Proxy Server Profile bound, or any AAA vserver has RDP enabled.
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
Apply the vendor-provided patch from Citrix for NetScaler ADC/Gateway. If immediate patching is not possible, consider disabling RDP-related features on affected VPN/AAA vservers as a temporary mitigation until the patch can be applied.
NetScaler ADC 12.1 -> 12.1-55.321; ADC 13.1 -> 13.1-55.34 or 13.1-37.207; ADC/Gateway 14.1 -> 14.1-29.72
- 1. Identify the current NetScaler ADC or Gateway version by running 'show version' or checking the management console
- 2. For NetScaler ADC 12.1: Upgrade to version 12.1-55.321 or later
- 3. For NetScaler ADC 13.1: Upgrade to version 13.1-55.34 or later (or 13.1-37.207 or later for the 13.1-37 branch)
- 4. For NetScaler ADC 14.1: Upgrade to version 14.1-29.72 or later
- 5. For NetScaler Gateway 13.1: Upgrade to version 13.1-55.34 or later
- 6. For NetScaler Gateway 14.1: Upgrade to version 14.1-29.72 or later
- 7. After upgrade, verify the fix by confirming the appliance does not have the vulnerable RDP configurations listed in the CVE description
- 8. Alternatively, if upgrading is not immediately possible, ensure the appliance is NOT configured as: (a) Gateway (VPN Vserver) with RDP Feature enabled, (b) Gateway with RDP Proxy Server Profile set to Gateway, or (c) Auth Server (AAA Vserver) with RDP Feature enabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8534 — 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-8534 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