dbcve.org
Application Delivery Controller FirmwareOperating system · Citrix

CVE-2019-18177

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-26
Fix available
A fix is available. Upgrade to 13.0-58.30 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
In certain Citrix products, information disclosure can be achieved by an authenticated VPN user when there is a configured SSL VPN endpoint. This affects Citrix ADC and Citrix Gateway 13.0-58.30 and later releases before the CTX276688 update.

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

An authenticated VPN user can obtain sensitive information disclosure in Citrix ADC and Citrix Gateway when an SSL VPN endpoint is configured. The vulnerability exists in versions 13.0-58.30 through versions prior to the CTX276688 patch.

MitigationApply the CTX276688 update/patch to Citrix ADC and Citrix Gateway installations to remediate the information disclosure vulnerability.

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:< 13.0-58.30
GatewayApplication
Affected:< 13.0-58.30

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 product and version
    Access the Citrix ADC or Gateway management interface or use the 'show version' command via SSH/CLI to determine the firmware version installed
    Affected if The firmware version is 13.0-58.30 or any version prior to it (e.g., 13.0-55.x, 13.0-40.x, etc.)
  2. Confirm product type is affected
    Verify the device is either Citrix Application Delivery Controller (ADC) or Citrix Gateway - the CVE only applies to these products
    Affected if The device is running Citrix ADC or Citrix Gateway software
  3. Check if SSL VPN is configured
    Review the VPN configuration through the management GUI under 'SSL VPN' settings or use 'show run' command to search for SSL VPN-related configurations (keywords: sslvpn, vpn, ssl vpn)
    Affected if An SSL VPN endpoint is configured and active on the device

A user is affected if the device runs Citrix ADC or Citrix Gateway firmware version 13.0-58.30 or lower AND has an SSL VPN endpoint configured.

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-58.30 or later
Fixed in 13.0-58.30
Interim mitigation

Apply the CTX276688 update/patch to Citrix ADC and Citrix Gateway installations to remediate the information disclosure vulnerability.

Recommended fix Moderate confidence

Citrix ADC/Gateway firmware 13.0-58.30 or later (including CTX276688 update)

  1. 1. Identify the current firmware version of the Citrix ADC or Citrix Gateway by checking the system information or running the 'show version' command
  2. 2. If the current version is below 13.0-58.30, plan for a firmware upgrade to version 13.0-58.30 or later
  3. 3. Before upgrading, review Citrix upgrade documentation and ensure backup of current configuration
  4. 4. Perform the firmware upgrade to version 13.0-58.30 or the latest stable 13.0 release
  5. 5. After upgrade, verify the system is functioning correctly and the SSL VPN endpoint is operational
  6. 6. Apply any subsequent updates such as CTX276688 when available

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

Fix this in Application Delivery Controller Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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