dbcve.org
Wide Area Application ServicesApplication · Cisco

CVE-2014-2196

HIGH · 9.3 CVSS v2.0 Published 2014-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Cisco Wide Area Application Services (WAAS) 5.1.1 before 5.1.1e, when SharePoint prefetch optimization is enabled, allows remote SharePoint servers to execute arbitrary code via a malformed response, aka Bug ID CSCue18479.

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 confidence

Cisco WAAS versions 5.1.1 before 5.1.1e contain a code injection vulnerability when SharePoint prefetch optimization is enabled. A malicious or compromised remote SharePoint server can send a malformed response that triggers arbitrary code execution on the WAAS device.

MitigationUpgrade Cisco WAAS to version 5.1.1e or later. If immediate upgrade is not possible, disable SharePoint prefetch optimization as a temporary workaround.

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
Wide Area Application ServicesApplication
Affected:= 5.1.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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/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 checks

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

  1. Identify Cisco WAAS installation and version
    Run the command to display the WAAS software version (such as 'show version' or similar CLI command depending on your WAAS deployment)
    Affected if The installed version is 5.1.1 specifically
  2. Confirm version is the vulnerable release
    Compare the displayed version number to the affected range - the vulnerability exists in version 5.1.1 before the 5.1.1e patch
    Affected if Running exactly version 5.1.1 (versions 5.1.1e and later contain the fix)
  3. Check if SharePoint prefetch optimization is enabled
    Inspect the WAAS configuration for SharePoint optimization settings - look for prefetch or SharePoint acceleration features in the WAAS policy or application settings
    Affected if SharePoint prefetch optimization is enabled (this feature must be active for the malformed response to trigger code execution)

Environment is affected if running Cisco WAAS version 5.1.1 with SharePoint prefetch optimization enabled, as the combination of this specific version and this specific feature allows the code injection to occur.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco WAAS to version 5.1.1e or later. If immediate upgrade is not possible, disable SharePoint prefetch optimization as a temporary workaround.

Recommended fix High confidence

Cisco WAAS 5.1.1e or later

  1. Identify current WAAS version using 'show version' command
  2. If immediate upgrade is not possible, disable SharePoint prefetch optimization as temporary mitigation: use the 'sharepoint-prefetch' configuration command to disable
  3. Schedule maintenance window for upgrade
  4. Download Cisco WAAS version 5.1.1e or later from Cisco (requires valid service contract)
  5. Backup current WAAS configuration
  6. Upgrade WAAS software using 'install' command or through centralized management interface
  7. Verify upgrade was successful with 'show version' command
  8. Re-enable SharePoint prefetch optimization if it was previously disabled and upgrade is confirmed
Caveat Review Cisco release notes for 5.1.1e for any compatibility considerations or known issues before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wide Area Application Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-2196 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