Application Delivery Controller FirmwareOperating system · Citrix

CVE-2021-22927

HIGH · 8.1 CVSS v3.1 Published 2021-08-05
Fix available
A fix is available. Upgrade to 11.1-65.22 / 12.1-55.238 or later.
See remediation →
88/100
Remediation priority · High
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
A session fixation vulnerability exists in Citrix ADC and Citrix Gateway 13.0-82.45 when configured SAML service provider that could allow an attacker to hijack a session.

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 confidence

Citrix ADC and Citrix Gateway 13.0-82.45 contain a session fixation vulnerability when configured as a SAML service provider. An attacker can potentially set or fix a user's session ID before authentication and then hijack the authenticated session, gaining unauthorized access.

MitigationUpgrade Citrix ADC and Citrix Gateway to a patched version beyond 13.0-82.45. For immediate mitigation, review SAML SP session handling configurations and consider implementing session ID regeneration after authentication.

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
Application Delivery Controller FirmwareOperating system
Affected:>= 11.1, < 11.1-65.22>= 12.1, < 12.1-62.27>= 13.0, < 13.0-82.45>= 12.1, < 12.1-55.238
GatewayApplication
Affected:>= 12.1, < 12.1-62.27>= 13.0, < 13.0-82.45
Netscaler GatewayApplication
Affected:>= 11.1, < 11.1-65.22

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 device product and firmware version
    Log into the Citrix ADC/Gateway CLI and run 'show version' or access the GUI under System > Information to view the firmware build number
    Affected if The version falls within any of these ranges: 11.1 before 65.22, 12.1 before 62.27 (or before 55.238 for certain builds), or 13.0 before 82.45
  2. Confirm the device is configured as a SAML Service Provider
    In the CLI run 'show samlIdpProfile' or 'show samlSPProfile' to list SAML configurations; in the GUI navigate to Citrix Gateway > SAML IdP or SAML SP to verify if any SAML service provider profile exists
    Affected if A SAML SP (Service Provider) profile is configured on the device
  3. Verify SAML SP session handling settings
    Run 'show samlSPProfile <profile_name>' or inspect the SAML SP configuration in the GUI under SAML SP settings to check if session tokens are being regenerated after authentication
    Affected if Session ID is not being regenerated post-authentication (this confirms the vulnerable configuration pattern for this CVE)

A device is affected if it is running a Citrix ADC, Citrix Gateway, or Netscaler Gateway firmware version in the affected ranges AND has a SAML Service Provider profile configured, enabling an attacker to fix the session ID before authentication.

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.

From vendor data
Upgrade available Upgrade to 11.1-65.22 / 12.1-55.238 / 12.1-62.27 or later
Fixed in 11.1-65.2212.1-55.23812.1-62.27
Interim mitigation

Upgrade Citrix ADC and Citrix Gateway to a patched version beyond 13.0-82.45. For immediate mitigation, review SAML SP session handling configurations and consider implementing session ID regeneration after authentication.

Fix this in Application Delivery Controller Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22927 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22927 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