CVE-2019-12991
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 · uneditedCitrix SD-WAN 10.2.x before 10.2.3 and NetScaler SD-WAN 10.0.x before 10.0.8 have Improper Input Validation (issue 5 of 6).
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 confidenceCitrix SD-WAN 10.2.x before 10.2.3 and NetScaler SD-WAN 10.0.x before 10.0.8 contain an improper input validation vulnerability, likely allowing attackers to inject malicious input that could be processed without adequate sanitization, potentially leading to injection attacks or unexpected behavior.
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>= 10.0.0, < 10.0.8>= 10.2.0, < 10.2.3CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SD-WAN product variantAccess the SD-WAN appliance management interface or CLI and determine if the product is labeled as 'Citrix NetScaler SD-WAN' or 'Citrix SD-WAN'. The product name is typically displayed on the login page or in the system information section.Affected if The product is either Citrix NetScaler SD-WAN or Citrix SD-WAN.
-
Determine the installed software versionLog into the SD-WAN web management console and navigate to the 'System', 'Statistics', or 'About' section to view the running software version. Alternatively, use the CLI command 'show version' or 'system info' to retrieve the version number.Affected if The version displayed is 10.0.x where x is less than 8, or 10.2.x where x is less than 3.
-
Compare version against affected rangesMatch the identified version number to the vulnerable ranges: NetScaler SD-WAN versions 10.0.0 through 10.0.7 (any 10.0.x below 10.0.8), and Citrix SD-WAN versions 10.2.0 through 10.2.2 (any 10.2.x below 10.2.3).Affected if The installed version falls within 10.0.0 to 10.0.7 or 10.2.0 to 10.2.2.
-
Verify management interface accessibilityCheck network configuration to determine if the SD-WAN management interface (HTTP/HTTPS on ports 80/443 or the dedicated management port) is reachable from untrusted networks. Review firewall rules, ACLs, and interface bindings.Affected if The management interface is accessible from networks outside the trusted administrative zone.
You are affected if your SD-WAN runs Citrix NetScaler SD-WAN version 10.0.x below 10.0.8 or Citrix SD-WAN version 10.2.x below 10.2.3, and the management interface is exposed to network paths where untrusted input could be submitted.
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 · scoped10.0.810.2.3
Upgrade Citrix SD-WAN to version 10.2.3 or later, or NetScaler SD-WAN to version 10.0.8 or later, to remediate this improper input validation vulnerability.
Citrix SD-WAN 10.0.8 (for 10.0.x branch) or 10.2.3 (for 10.2.x branch)
- 1. Back up current SD-WAN configuration and ensure you have a recovery mechanism
- 2. Download the fixed SD-WAN release from Citrix support portal: version 10.0.8 for 10.0.x branch or version 10.2.3 for 10.2.x branch
- 3. Plan maintenance window as upgrade may cause brief network interruption
- 4. Upload the new firmware/software version to the SD-WAN appliance
- 5. Initiate the upgrade following Citrix SD-WAN upgrade procedures
- 6. Verify the upgrade completed successfully
- 7. Validate that all SD-WAN services are functioning normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12991 — 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-2019-12991 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