Netscaler Application Delivery Controller FirmwareOperating system · Citrix

CVE-2013-6938

MEDIUM · 5.0 CVSS v2.0 Published 2014-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the Service VM in Citrix NetScaler SDX 9.3 before 9.3-64.4 and 10.0 before 10.0-77.5 and 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 allows attackers to cause a denial of service via unknown vectors, related to the "Virtual Machine Daemon."

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 confidence

Denial of service vulnerability in the Virtual Machine Daemon component of the Service VM in Citrix NetScaler SDX and ADC appliances. The vulnerability allows remote attackers to cause a DoS condition through unknown attack vectors targeting the VM daemon service.

MitigationApply Citrix patches 9.3-64.4, 10.0-77.5, or 10.1-118.7 (or later) to the affected NetScaler SDX and ADC deployments, and schedule appropriate maintenance windows for patch deployment.

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
Affected:= 9.3\(1\)= 9.3.e= 10.0= 10.1

CVSS 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
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NetScaler appliance model
    Access the appliance CLI via SSH or the management GUI. Run 'show hardware' or check the system information to confirm if the device is an SDX or ADC model.
    Affected if The device is a NetScaler SDX or ADC appliance running the affected firmware versions.
  2. Check the firmware version
    Run 'show version' in the CLI or view the version information in the management interface. Note the exact firmware build number.
    Affected if The firmware version is exactly 9.3(1), 9.3.e, 10.0, or 10.1 (without the cited security patches applied).
  3. Verify the Virtual Machine Daemon is in use
    Run 'show vm' or 'show service vm' in the CLI to check if the VM daemon service is configured. On SDX models, verify if the Service VM feature is enabled.
    Affected if The Virtual Machine Daemon or Service VM component is actively running on the appliance.
  4. Review recent daemon service logs
    Check /var/log/vm.log or run 'nslog' with VM daemon facility if accessible. Look for crash events, unexpected restarts, or error messages related to the VM daemon service.
    Affected if The logs show evidence of daemon crashes or unexpected service interruptions without an assigned cause.

You are affected if you run a NetScaler SDX or ADC appliance with firmware version 9.3(1), 9.3.e, 10.0, or 10.1 and the Virtual Machine Daemon or Service VM feature is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Citrix patches 9.3-64.4, 10.0-77.5, or 10.1-118.7 (or later) to the affected NetScaler SDX and ADC deployments, and schedule appropriate maintenance windows for patch deployment.

Fix this in Netscaler Application Delivery Controller Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6938 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-6938 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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