Netscaler Application Delivery Controller FirmwareOperating system · Citrix
CVE-2013-6940
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 NetScaler Application Delivery Controller (ADC) 9.3.x before 9.3-64.4, 10.0 before 10.0-77.5, and 10.1 before 10.1-118.7 logs user credentials, which allows attackers to obtain sensitive information via unspecified vectors.
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 confidenceCitrix NetScaler ADC versions 9.3.x before 9.3-64.4, 10.0 before 10.0-77.5, and 10.1 before 10.1-118.7 contain a vulnerability where user credentials are inadvertently written to system log files. An attacker with access to these logs (through log management systems, storage access, or log injection) can retrieve plaintext credentials.
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
Netscaler Application Delivery Controller FirmwareOperating system
= 9.3\(1\)= 9.3.e= 10.0= 10.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 NetScaler ADC firmware versionRun the command 'show version' in the NetScaler command line interface or check the System > Diagnostics > Version Information page in the web management interfaceAffected if The version shown is 9.3.x before 9.3-64.4, 10.0 before 10.0-77.5, or 10.1 before 10.1-118.7, including the specific versions 9.3(1), 9.3.e, 10.0, or 10.1
-
Locate system log files containing user authentication eventsAccess log files in /var/log/ directory, typically ns.log, nsconfig.log, or authentication-related logs. In the web interface, check System > Diagnostics > Audit Logging or System > Diagnostics > Messages for authentication eventsAffected if Log files exist and contain entries from the affected version range
-
Search log files for plaintext password patternsUse the command 'grep -i password' on log files in /var/log/ or use the log viewer to search for authentication-related entries. Look for strings matching login attempts, user= or password= patterns in plaintextAffected if Log entries contain plaintext password strings or credentials visible in the log output
The system is affected if the NetScaler ADC firmware version is 9.3.x before 9.3-64.4, 10.0 before 10.0-77.5, or 10.1 before 10.1-118.7 AND plaintext credentials are found in the system logs.
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.
From vendor dataUpgrade NetScaler ADC to version 9.3-64.4, 10.0-77.5, 10.1-118.7 or later. Additionally, review existing log files for credential exposure and rotate credentials that may have been logged.
Fix this in Netscaler Application Delivery Controller Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6940 — 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-2013-6940 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