CVE-2023-24487
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 · uneditedArbitrary file read in Citrix ADC and Citrix Gateway
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 confidenceAn arbitrary file read vulnerability in Citrix ADC and Citrix Gateway allows an attacker to read sensitive files on the system they should not have access to, potentially exposing configuration files, credentials, or other sensitive data.
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>= 12.1, < 12.1-55.296>= 12.1, < 12.1-65.35>= 13.0, < 13.0-90.11>= 13.1, < 13.1-37.150>= 13.1, < 13.1-45.61>= 12.1, < 12.1-65.35>= 13.0, < 13.0-90.11>= 13.1, < 13.1-45.61CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionLog into the Citrix ADC or Gateway CLI and run 'show version' or check the management interface for the build numberAffected if The displayed version falls within any of the affected ranges: 12.1 before 12.1-55.296 or 12.1-65.35; 13.0 before 13.0-90.11; 13.1 before 13.1-37.150 or 13.1-45.61
-
Confirm product typeVerify whether the installed system is Citrix ADC, Citrix Gateway, or a combined deployment using 'show ns version' or checking the license and feature setAffected if The device runs Citrix ADC or Citrix Gateway in any affected version
-
Check management interface exposureDetermine if the management interface (NSIP, VIP, or SSL VPN portal) is accessible from untrusted networks by reviewing network configurations and firewall rulesAffected if The management or VPN portal is exposed to the internet or untrusted networks without proper access controls
-
Review audit and access logsSearch system logs and audit logs for unusual or unauthorized file read requests, particularly to system configuration files or sensitive directoriesAffected if Logs contain requests for files outside normal administrative operations, especially from external IP addresses
-
Check for unauthorized configuration exportsLook for evidence of unsanctioned 'ns.conf' exports, directory traversal patterns in logs, or unexpected configuration file accessAffected if Logs or file system show evidence of arbitrary file read attempts or unauthorized configuration exports
You are affected if your Citrix ADC or Gateway version is one of the listed versions and the management interface is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.1-55.29612.1-65.3513.0-90.11
Apply Citrix security updates immediately. If patches are unavailable, restrict network access to management interfaces and monitor for unusual file access patterns.
Citrix ADC: 13.1-37.150 or later; Citrix Gateway: 13.1-45.61 or later (or equivalent 12.1/13.0 fixes per branch)
- 1. Identify the exact Citrix ADC or Gateway version currently installed using 'show version' command
- 2. For Citrix ADC: Upgrade to version 12.1-55.296 or higher (12.1 branch), or 12.1-65.35 or higher, or 13.0-90.11 or higher, or 13.1-37.150 or higher depending on your baseline
- 3. For Citrix Gateway: Upgrade to version 12.1-65.35 or higher, or 13.0-90.11 or higher, or 13.1-45.61 or higher depending on your baseline
- 4. Download the appropriate build from support.citrix.com
- 5. Install the upgrade following Citrix documentation - typically via the 'install' command or through the management interface
- 6. Verify the upgrade was successful with 'show version'
- 7. Confirm the vulnerability is resolved by checking the build number matches or exceeds the fixed versions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24487 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-24487 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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