dbcve.org
Application Delivery ManagementApplication · Citrix

CVE-2022-27511

HIGH · 8.1 CVSS v3.1 Published 2022-06-16
Fix available
A fix is available. Upgrade to 13.0-85.19 / 13.1-21.53 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Corruption of the system by a remote, unauthenticated user. The impact of this can include the reset of the administrator password at the next device reboot, allowing an attacker with ssh access to connect with the default administrator credentials after the device has rebooted.

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

A remote unauthenticated attacker can corrupt the system, which causes the administrator password to reset to default upon the next device reboot. After reboot, the attacker can gain SSH access using the default administrator credentials.

MitigationApply the vendor patch or firmware update for CVE-2022-27511. If immediate patching is not possible, monitor for unauthorized access and consider network segmentation to limit exposure to untrusted networks.

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 ManagementApplication
Affected:< 13.0-85.19>= 13.1, < 13.1-21.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
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 checks

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

  1. Identify if Citrix Application Delivery Management is installed
    Check for running ADM processes or services. On Linux: 'ps aux | grep -i citrix' or 'systemctl list-units | grep -i adm'. On the appliance interface, check the system information page.
    Affected if Citrix ADM is running on the system
  2. Determine the installed Citrix ADM version
    Log into the Citrix ADM web interface and navigate to System > System Information, or run 'show version' via CLI. Compare the version number against the affected ranges: < 13.0-85.19 or >= 13.1 and < 13.1-21.53.
    Affected if The installed version falls within < 13.0-85.19 or >= 13.1, < 13.1-21.53
  3. Check if SSH access is enabled on the appliance
    In the web interface, go to System > Settings > SSH Settings, or run 'show ssh' via CLI. Verify whether SSH service is enabled and accessible from network interfaces exposed to untrusted networks.
    Affected if SSH is enabled and the management interface is reachable from untrusted networks
  4. Verify administrator password integrity
    After a suspected attack or unexpected system corruption, attempt to log in with default admin credentials (nsroot/nsroot) or check if the administrator password has been reset to default.
    Affected if The default administrator credentials work or password has been reset

A user is affected if they are running a vulnerable Citrix ADM version (below 13.0-85.19 or between 13.1 and 13.1-21.53) with SSH access exposed to untrusted networks, allowing an attacker to reset the admin password to default.

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 13.0-85.19 / 13.1-21.53 or later
Fixed in 13.0-85.1913.1-21.53
Interim mitigation

Apply the vendor patch or firmware update for CVE-2022-27511. If immediate patching is not possible, monitor for unauthorized access and consider network segmentation to limit exposure to untrusted networks.

Recommended fix Moderate confidence

13.0-85.19 or later for 13.0.x branch; 13.1-21.53 or later for 13.1.x branch

  1. Back up the current Citrix Application Delivery Management configuration and take note of the current version
  2. Navigate to the Citrix support portal (support.citrix.com) and download the appropriate fixed release for your version branch
  3. For version 13.0.x: upgrade to version 13.0-85.19 or later
  4. For version 13.1.x: upgrade to version 13.1-21.53 or later
  5. Follow the official Citrix upgrade documentation for Application Delivery Management to apply the update
  6. After upgrade, verify the build version matches the fixed release
  7. Confirm administrator credentials are working and review access control settings
  8. Ensure SSH access is restricted to authorized users only
Caveat Review Citrix release notes for any known issues or migration considerations between versions; ensure compatibility with connected NetScaler instances

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

Fix this in Application Delivery Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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