dbcve.org
Application Delivery ManagementApplication · Citrix

CVE-2022-27512

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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
Temporary disruption of the ADM license service. The impact of this includes preventing new licenses from being issued or renewed by Citrix ADM.

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

This is a denial-of-service vulnerability in Citrix Application Delivery Management (ADM) license service. The vulnerability allows an attacker to temporarily disrupt the license service, preventing new licenses from being issued or renewed.

MitigationContact Citrix for the specific patch and implementation guidance. Given the limited scope of the disruption, verify license server redundancy and review Citrix ADM hardening documentation while awaiting the vendor patch.

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

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

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. Determine Citrix ADM installed version
    Access the Citrix ADM management interface and navigate to the System > Diagnostics > Version Information page, or run 'show version' via the CLI. Note the full version string including the build number.
    Affected if The installed version is earlier than 13.0-85.19, OR is 13.1.x earlier than 13.1-21.53
  2. Verify license service is operational
    In the Citrix ADM GUI, navigate to the License section or run the appropriate CLI command to check license server status. Confirm the license service responds to requests.
    Affected if The license service is running and accessible, making it vulnerable to disruption attempts
  3. Check network accessibility of ADM management interface
    Review network configuration to determine if the Citrix ADM management interface and license service ports are exposed to untrusted networks or the internet.
    Affected if The ADM interface or license service ports are reachable from untrusted networks, allowing remote attackers to trigger the DoS condition

A user is affected if their Citrix ADM version falls within the ranges of 13.0 before build 85.19 or 13.1 before build 21.53, and the license service is network-accessible.

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

Contact Citrix for the specific patch and implementation guidance. Given the limited scope of the disruption, verify license server redundancy and review Citrix ADM hardening documentation while awaiting the vendor patch.

Recommended fix Moderate confidence

Citrix ADM 13.0-85.19 or later, or 13.1-21.53 or later

  1. 1. Back up current Citrix ADM configuration and license data
  2. 2. Download the fixed ADM version (13.0-85.19 or later for 13.0.x branch, or 13.1-21.53 or later for 13.1.x branch) from Citrix support portal
  3. 3. Access ADM management interface and navigate to System -> Upgrade
  4. 4. Upload the upgrade package and initiate the upgrade process
  5. 5. Verify the license service is operational post-upgrade
  6. 6. Confirm new licenses can be issued and renewed
Caveat Standard upgrade risks apply - ensure backup before proceeding

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
  • 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-27512 — 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-27512 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