CVE-2023-4967
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 · uneditedDenial of Service in NetScaler ADC and NetScaler Gateway when configured as a Gateway (VPN virtual server, ICA Proxy, CVPN, RDP Proxy) or AAA Virtual Server
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 confidenceA denial of service vulnerability exists in NetScaler ADC and NetScaler Gateway when configured as a Gateway (including VPN virtual server, ICA Proxy, CVPN, or RDP Proxy) or AAA Virtual Server. An unauthenticated remote attacker can exploit this condition to cause a denial of service on the affected virtual server.
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>= 13.0, < 13.0-92.19>= 13.1, < 13.1-49.15>= 14.1, < 14.1-8.50>= 12.1, <= 12.1-55.300>= 13.1, <= 13.1-37.164>= 13.0, < 13.0-92.19>= 13.1, < 13.1-49.15>= 14.1, < 14.1-8.50CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetScaler product and versionRun 'show version' command on the NetScaler CLI or check the product version in the NetScaler GUI under System > Information > LicenseAffected if The installed version is 13.0 before 13.0-92.19, 13.1 before 13.1-49.15, 14.1 before 14.1-8.50, 12.1 up to 12.1-55.300, or 13.1 up to 13.1-37.164
-
Confirm product type is ADC or GatewayRun 'show ns version' or check the licensed product type in NetScaler GUI under System > LicensingAffected if The product is NetScaler ADC or NetScaler Gateway
-
Check for Gateway virtual server configurationRun 'show vserver' command and look for VPN virtual servers, ICA Proxy, CVPN, or RDP Proxy typesAffected if Any virtual server is configured as VPN, ICA Proxy, CVPN, or RDP Proxy type
-
Check for AAA virtual server configurationRun 'show aaa vserver' command to list AAA virtual serversAffected if Any AAA virtual server is configured and enabled
You are affected if you are running a vulnerable NetScaler ADC or Gateway version AND have a Gateway virtual server (VPN, ICA Proxy, CVPN, or RDP Proxy) OR an AAA virtual server configured.
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 · scoped13.0-92.1913.1-49.1514.1-8.50
Apply the relevant Citrix security update for NetScaler ADC and NetScaler Gateway. Until patches can be applied, consider implementing rate limiting or access controls on affected virtual servers to reduce exposure.
Upgrade to the minimum fixed build for your branch: 13.0-92.19 (13.0 branch), 13.1-49.15 (13.1 branch), 14.1-8.50 (14.1 branch), or latest available for 12.1
- 1. Identify the currently installed NetScaler ADC or Gateway version via the CLI command 'show version' or the GUI under System > Information
- 2. Determine which version branch you are running (12.1, 13.0, 13.1, or 14.1)
- 3. For version 12.1: Upgrade to the latest available build (12.1-55.300 or later if available) as this branch has limited remaining support
- 4. For version 13.0: Upgrade to build 13.0-92.19 or later
- 5. For version 13.1: Upgrade to build 13.1-49.15 or later
- 6. For version 14.1: Upgrade to build 14.1-8.50 or later
- 7. After upgrade, verify the fix by checking 'show version' confirms the new build number
- 8. Test that Gateway services (VPN virtual server, ICA Proxy, CVPN, RDP Proxy) and AAA Virtual Server are functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4967 — 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-4967 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