dbcve.org
GatewayApplication · Citrix

CVE-2022-27509

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 12.1-55.282 / 12.1-65.15 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
Unauthenticated redirection to a malicious website

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

Unauthenticated open redirect vulnerability allowing attackers to craft malicious URLs that redirect victims to external malicious websites. This can be leveraged for phishing attacks as users trust URLs originating from the legitimate application.

MitigationImplement strict validation of redirect URLs to ensure they are relative paths or point to an allowed list of trusted domains; reject or sanitize any user-supplied redirect parameters containing absolute URLs to external sites.

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
GatewayApplication
Affected:>= 12.1, < 12.1-65.15>= 13.0, < 13.0-86.17>= 13.1, < 13.1-24.38
Application Delivery Controller FirmwareOperating system
Affected:>= 12.1, < 12.1-65.15>= 13.0, < 13.0-86.17>= 13.1, < 13.1-24.38>= 12.1, < 12.1-55.282

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 installed Citrix product version
    Access the CLI and run 'show version' or 'nsversion' command; alternatively, check the web interface login page footer which often displays the firmware version
    Affected if The displayed version falls within these ranges: 12.1 through 12.1-65.14, 13.0 through 13.0-86.16, 13.1 through 13.1-24.37, or 12.1 through 12.1-55.281 (specific to ADC firmware)
  2. Confirm product type is affected
    Run 'show hardware' or 'show ns info' in the CLI to confirm whether the device is running Citrix Gateway or Citrix Application Delivery Controller (ADC) firmware
    Affected if The device is a Citrix Gateway or ADC running an affected firmware version from the ranges above
  3. Check network exposure of the login interface
    Determine if the Citrix Gateway or ADC web login page (typically on ports 443 or 8443) is accessible from untrusted networks or the internet
    Affected if The gateway login page is externally accessible without VPN or other access controls, since the open redirect can be exploited without authentication

You are affected if your Citrix Gateway or ADC firmware version is within the vulnerable ranges AND the login interface is accessible to untrusted users who could be redirected to malicious external sites.

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.282 / 12.1-65.15 / 13.0-86.17 or later
Fixed in 12.1-55.28212.1-65.1513.0-86.17
Interim mitigation

Implement strict validation of redirect URLs to ensure they are relative paths or point to an allowed list of trusted domains; reject or sanitize any user-supplied redirect parameters containing absolute URLs to external sites.

Recommended fix Moderate confidence

12.1-65.15 (or later) | 13.0-86.17 (or later) | 13.1-24.38 (or later) depending on version branch

  1. 1. Identify the current installed version of Citrix Gateway or Application Delivery Controller (ADC) via the management console or CLI using 'show version'
  2. 2. Determine which version branch your current installation belongs to (12.1, 13.0, or 13.1)
  3. 3. For Gateway/ADC version 12.1.x: Plan upgrade to version 12.1-65.15 or later (or 12.1-55.282+ for ADC Firmware specifically)
  4. 4. For version 13.0.x: Plan upgrade to version 13.0-86.17 or later
  5. 5. For version 13.1.x: Plan upgrade to version 13.1-24.38 or later
  6. 6. Download the appropriate firmware/iso from Citrix official support portal (support.citrix.com) after authentication
  7. 7. Review Citrix upgrade documentation and release notes for your specific product
  8. 8. Perform upgrade during a planned maintenance window following Citrix best practices
Caveat Review release notes for potential configuration or feature changes between versions; some upgrades may require specific migration steps

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

Fix this in Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27509 — 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-2022-27509 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