Netscaler Application Delivery Controller FirmwareOperating system · Citrix
CVE-2013-6011
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) 10.0 before 10.0-76.7 allows remote attackers to cause a denial of service (nsconfigd crash and appliance reboot) via a crafted request.
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 10.0 before version 10.0-76.7 contains a vulnerability that allows remote attackers to send a crafted request causing the nsconfigd service to crash, resulting in a denial of service condition that forces the appliance to reboot.
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
= 10.0= 10.0.e
Netscaler Application Delivery ControllerHardware / appliance
all versionsCVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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.
-
Determine NetScaler ADC firmware versionLog into the NetScaler command-line interface and run 'show version' or check the GUI under System > Information > Version. Record the full build number.Affected if The installed version is 10.0 or 10.0.e (any build) and is earlier than 10.0-76.7.
-
Compare version to the patched releaseTake the full version number from step 1 (format is typically 10.0-XXX.X) and compare it to 10.0-76.7.Affected if The numeric build is lower than 76.7 (for example, 10.0-70.5 or 10.0-76.6).
-
Verify nsconfigd service is runningLog into the NetScaler CLI and run 'show service' or check if the nsconfigd process is active using process status commands available on the appliance.Affected if The nsconfigd service is running and accessible, which is the default state on affected versions.
-
Confirm network accessibility of the ADC management interfaceVerify that the NetScaler ADC management interface (IP address) is reachable from network locations where attackers could send crafted requests.Affected if The management interface or NSIP is exposed to untrusted networks without proper access controls.
You are affected if your NetScaler ADC runs firmware version 10.0 or 10.0.e with a build number earlier than 10.0-76.7 and the nsconfigd service is accessible.
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 Citrix NetScaler ADC to version 10.0-76.7 or later to patch the vulnerability.
Fix this in Netscaler Application Delivery Controller Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6011 — 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-6011 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