Webex Meetings ServerApplication · Cisco

CVE-2014-3395

MEDIUM · 5.0 CVSS v2.0 Published 2014-09-30
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
Cisco WebEx Meetings Server (WMS) 2.5 allows remote attackers to trigger the download of arbitrary files via a crafted URL, aka Bug ID CSCup10343.

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

Cisco WebEx Meetings Server (WMS) 2.5 contains a path traversal vulnerability that allows remote attackers to download arbitrary files from the server file system by crafting malicious URLs containing directory traversal sequences (e.g., ../../../'). This is an unauthenticated remote attack enabling information disclosure.

MitigationApply the vendor patch from Cisco for this vulnerability or upgrade to a patched version of WMS. As an interim control, deploy web application firewall (WAF) rules or URL filtering to block requests containing directory traversal patterns.

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
Webex Meetings ServerApplication
Affected:= 2.5

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
None
Availability
None

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

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. Confirm Cisco WebEx Meetings Server is deployed
    Identify if Cisco WebEx Meetings Server (WMS) is installed in your environment by reviewing installed software, services, or documentation. Look for WMS-specific processes or the product name in your asset inventory.
    Affected if WMS is present in the environment
  2. Determine installed WMS version
    Check the installed version of Cisco WebEx Meetings Server using vendor documentation methods such as the admin interface, version display command, or configuration files. Compare the version number to 2.5.
    Affected if The installed version is exactly 2.5
  3. Verify web service is accessible
    Determine if the WMS web interface is reachable from network locations by testing HTTP/HTTPS access to the WMS host on common ports (typically 443 or 8443).
    Affected if WMS web service is externally or internally accessible without authentication
  4. Test for directory traversal vulnerability
    Send a crafted HTTP request containing directory traversal sequences (such as ../../../etc/passwd or similar paths) to the WMS web server and observe if the server returns file contents outside the web root.
    Affected if The server returns arbitrary file contents in response to traversal sequences, indicating the vulnerability is present and exploitable
  5. Review logs for exploitation attempts
    Examine WMS access and error logs for requests containing ../ patterns or directory traversal sequences, which may indicate attempted or successful exploitation.
    Affected if Logs show requests with directory traversal patterns directed at WMS

You are affected if Cisco WebEx Meetings Server version 2.5 is running and its web interface is accessible, allowing unauthenticated path traversal attacks to read arbitrary files.

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 the vendor patch from Cisco for this vulnerability or upgrade to a patched version of WMS. As an interim control, deploy web application firewall (WAF) rules or URL filtering to block requests containing directory traversal patterns.

Fix this in Webex Meetings Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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