Wide Area Application Services MobileApplication · Cisco

CVE-2013-5554

HIGH · 7.5 CVSS v2.0 Published 2013-11-08
Fix available
A fix is available. Upgrade to after 3.5.4 or later.
See remediation →
84/100
Remediation priority · High
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
Directory traversal vulnerability in the web-management interface in the server in Cisco Wide Area Application Services (WAAS) Mobile before 3.5.5 allows remote attackers to upload and execute arbitrary files via a crafted POST request, aka Bug ID CSCuh69773.

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

A directory traversal vulnerability exists in the web-management interface of Cisco WAAS Mobile versions prior to 3.5.5. Attackers can craft malicious POST requests to upload files to arbitrary locations on the filesystem and subsequently execute them, achieving remote code execution.

MitigationUpgrade Cisco WAAS Mobile to version 3.5.5 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the management interface using firewalls or ACLs.

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 Services MobileApplication
Affected:<= 3.5.4= 3.3.1= 3.3.4= 3.4= 3.4.1= 3.4.2= 3.5.0= 3.5.1= 3.5.2= 3.5.3

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/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 if Cisco WAAS Mobile is installed
    Locate the WAAS Mobile installation directory or check running processes for WAAS Mobile components. On Windows, check Add/Remove Programs or installed services; on Linux, check for waas or widearea processes.
    Affected if Cisco WAAS Mobile software is present on the system
  2. Check the installed WAAS Mobile version
    Access the web-management interface and navigate to the About or Version page, or run the command-line tool 'waas version' if available. Compare the version number against the affected list: <= 3.5.4, 3.3.1, 3.3.4, 3.4, 3.4.1, 3.4.2, 3.5.0, 3.5.1, 3.5.2, 3.5.3.
    Affected if The installed version matches any version listed in the affected products and versions
  3. Confirm the web-management interface is enabled
    Log into the WAAS Mobile admin console or check the configuration file for web management settings. Look for HTTP/HTTPS listener status on the management port (default is typically TCP 8443 or similar).
    Affected if The web-management interface is active and listening for connections
  4. Verify network accessibility of the management interface
    Check firewall rules, ACLs, or network segmentation to determine if the management port is exposed to untrusted networks. Use netstat or port scanning tools to identify listening management ports and their binding addresses.
    Affected if The management interface is reachable from networks other than trusted administration segments

A system is affected if Cisco WAAS Mobile version 3.5.4 or below is installed AND the web-management interface is enabled and accessible to the attacker.

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
Upgrade available Upgrade to a release after 3.5.4
Interim mitigation

Upgrade Cisco WAAS Mobile to version 3.5.5 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the management interface using firewalls or ACLs.

Fix this in Wide Area Application Services Mobile Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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