Adaptive Security Appliance SoftwareApplication · Cisco
CVE-2013-6691
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 · uneditedThe WebVPN CIFS implementation in Cisco Adaptive Security Appliance (ASA) Software 9.0(.4.1) and earlier allows remote CIFS servers to cause a denial of service (device reload) via a long share list, aka Bug ID CSCuj83344.
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 confidenceThe vulnerability exists in Cisco ASA's WebVPN CIFS (Common Internet File System) implementation. A remote CIFS server can send a specially crafted long share list that causes the ASA device to reload, resulting in denial of service. This is a parsing/processing flaw in how the ASA handles CIFS share responses from servers.
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
Adaptive Security Appliance SoftwareApplication
<= 9.0\(4.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
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/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.
-
Check ASA software versionRun the command 'show version' on the ASA CLI. Locate the 'Software Version' line in the output.Affected if The displayed version number is 9.0(4.1) or any earlier version in the 9.0.x line.
-
Verify WebVPN is enabledRun 'show run webvpn' to view the WebVPN configuration. Also run 'show vpn-sessiondb webvpn' to check for active WebVPN sessions.Affected if WebVPN is configured and enabled (any output returned from these commands indicates WebVPN is active).
-
Confirm CIFS browsing is configuredRun 'show run | include cifs' to search for CIFS-related commands in the configuration. Look specifically for 'cifs enable' or 'cifs' under the webvpn context.Affected if CIFS browsing is enabled in the WebVPN configuration (the command returns CIFS-related configuration lines).
-
Check configured CIFS serversRun 'show run webvpn' and look for 'cifs server' entries that define CIFS server addresses for the WebVPN CIFS proxy.Affected if One or more CIFS servers are configured in the WebVPN settings.
You are affected if your ASA runs software version 9.0(4.1) or lower AND WebVPN with CIFS browsing is enabled and a CIFS server is 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.
From vendor dataUpgrade Cisco ASA Software to a version newer than 9.0.4.1 to patch the vulnerability. If immediate patching is not feasible, restrict CIFS server connections using access controls and monitor for unusual CIFS traffic patterns.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6691 — 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-6691 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