dbcve.org
Netscaler Application Delivery ControllerApplication · Citrix

CVE-2024-5492

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 12.1-55.304 / 13.0-92.31 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Open redirect vulnerability allows a remote unauthenticated attacker to redirect users to arbitrary websites in NetScaler ADC and NetScaler Gateway

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 confidence

Open redirect vulnerability in NetScaler ADC and NetScaler Gateway that allows unauthenticated remote attackers to craft malicious URLs containing arbitrary redirect targets, potentially tricking users into visiting phishing or malicious sites.

MitigationApply vendor-provided patches for NetScaler ADC and NetScaler Gateway. Until patched, implement URL validation at upstream proxies or WAFs to filter suspicious redirect parameters.

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
Netscaler Application Delivery ControllerApplication
Affected:>= 12.1, < 12.1-55.304>= 12.1, < 13.0-92.31>= 13.1, < 13.1-37.183>= 13.1, < 13.1-53.17>= 14.1, < 14.1-25.53
Netscaler GatewayApplication
Affected:>= 12.1, < 13.0-92.31>= 13.1, < 13.1-53.17>= 14.1, < 14.1-25.53

CVSS 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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed NetScaler product
    Access the NetScaler command line (nscli) or web interface. Run 'show version' or check the system information page to confirm whether the device is NetScaler ADC or NetScaler Gateway.
    Affected if The device is running NetScaler ADC or NetScaler Gateway.
  2. Determine the NetScaler version
    Run 'show version' from the nscli or check Help > About in the web interface. Note the full version number including the build (for example, 13.1-37.183).
    Affected if The version matches any of the affected ranges: 12.1 before 12.1-55.304, 13.0 before 13.0-92.31, 13.1 before 13.1-37.183 or 13.1-53.17 (depending on the build), or 14.1 before 14.1-25.53.
  3. Confirm the web login interface is exposed
    Check network configuration with 'show ip' or review the vserver configuration to see if the management or logon URLs are bound to a publicly accessible IP address. Use a browser or curl to verify the login page is reachable from external networks.
    Affected if The NetScaler logon page (typically /) is accessible from untrusted networks without VPN or authentication.
  4. Inspect URL parameters for redirect behavior
    Use a browser or curl to test URL patterns on the login page. Observe whether any URL parameters (such as 'url=', 'target=', 'redirect=', or similar) cause the application to return a 302 redirect to an external domain. Example test: curl -I 'https://<netscaler>/logon/LogonPoint/redirect.html?url=http://evil.com'
    Affected if The application returns a Location header pointing to an external domain controlled by an attacker when arbitrary values are passed in URL parameters.

The environment is affected if running a vulnerable version of NetScaler ADC or Gateway (matching the affected version ranges) with the web interface exposed externally and redirect parameters accepting arbitrary external URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 12.1-55.304 / 13.0-92.31 / 13.1-37.183 or later
Fixed in 12.1-55.30413.0-92.3113.1-37.183
Interim mitigation

Apply vendor-provided patches for NetScaler ADC and NetScaler Gateway. Until patched, implement URL validation at upstream proxies or WAFs to filter suspicious redirect parameters.

Recommended fix High confidence

NetScaler ADC: 12.1-55.304, 13.0-92.31, or 13.1-53.17 (or latest 13.1); NetScaler Gateway: 13.0-92.31, 13.1-53.17, or 14.1-25.53 (or latest 14.1)

  1. 1. Identify the current NetScaler ADC or NetScaler Gateway version by navigating to the System > Diagnostics > Show Version page in the management GUI or running 'show version' in the CLI
  2. 2. Based on your current major version, determine the minimum fixed build required: For ADC 12.1, upgrade to 12.1-55.304 or later; For ADC 13.0, upgrade to 13.0-92.31 or later; For ADC 13.1, upgrade to 13.1-53.17 or later; For Gateway 12.1, upgrade to 13.0-92.31 or later; For Gateway 13.1, upgrade to 13.1-53.17 or later; For Gateway 14.1, upgrade to 14.1-25.53 or later
  3. 3. Download the appropriate firmware build from the Citrix downloads portal (support.citrix.com)
  4. 4. Back up the current NetScaler configuration using 'save ns config' command and export the configuration file
  5. 5. Upload the new firmware build via the GUI (System > Firmware > Upload) or CLI ('install ns firmware')
  6. 6. Reboot the NetScaler appliance after firmware installation
  7. 7. Verify the upgrade was successful by checking the version and ensuring all services are running
  8. 8. Test that the open redirect vulnerability is remediated by attempting to access a URL with a redirect parameter to confirm proper validation
Caveat Review Citrix release notes for any deprecated features or configuration changes between versions; ensure HA pair upgrades are performed according to Citrix best practices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netscaler Application Delivery Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5492 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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