dbcve.org
Webex Meeting CenterApplication · Cisco

CVE-2014-0708

MEDIUM · 5.0 CVSS v2.0 Published 2014-03-21
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
WebEx Meeting Center in Cisco WebEx Business Suite does not properly compose URLs for HTTP GET requests, which allows remote attackers to obtain sensitive information by reading (1) web-server access logs, (2) web-server Referer logs, or (3) a browser's history, aka Bug ID CSCul98272.

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

WebEx Meeting Center in Cisco WebEx Business Suite improperly composes URLs for HTTP GET requests, causing sensitive information (likely authentication tokens, session identifiers, or user credentials) to be included in URL query strings. This exposes the sensitive data in web server access logs, Referer headers, and browser history, allowing remote attackers to obtain this information.

MitigationMigrate sensitive parameters from URL query strings to POST body parameters, secure HTTP-only cookies, or server-side session storage. Review and purge existing access and referer logs containing exposed sensitive data.

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 Meeting CenterApplication
Affected:all versions

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 Meeting Center is deployed
    Identify if your environment includes Cisco WebEx Meeting Center or Cisco WebEx Business Suite by reviewing installed software, service inventory, or consulting with your IT administration team
    Affected if The product is present in the environment
  2. Inspect URLs for sensitive parameters in query strings
    Use browser developer tools or a network proxy to capture login and authentication requests to your WebEx server. Examine the URL query strings for visible session tokens, authentication credentials, or user identifiers
    Affected if Sensitive authentication data (tokens, session IDs, credentials) appears in URL query strings rather than in POST body parameters
  3. Review web server access logs for sensitive data in URLs
    Locate and search your WebEx server access logs (typically in /var/log/httpd/, /var/log/nginx/, or similar platform-specific log directories) for entries containing your WebEx URL paths with query parameters. Search for patterns matching authentication tokens, session IDs, or credential-like strings in the request URL field
    Affected if Access logs contain sensitive authentication data in URL query strings
  4. Check Referer headers for exposed credentials
    Examine your upstream proxy, firewall, or application logs for Referer header entries pointing to your WebEx server. Verify if these Referer URLs contain sensitive parameters in query strings that could be passed to third-party sites
    Affected if Referer headers logged from WebEx requests contain sensitive query parameters

If Cisco WebEx Meeting Center is in use and sensitive authentication data is found in URL query strings (visible in network traces, access logs, or Referer headers), the environment is affected by this vulnerability.

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

Migrate sensitive parameters from URL query strings to POST body parameters, secure HTTP-only cookies, or server-side session storage. Review and purge existing access and referer logs containing exposed sensitive data.

Fix this in Webex Meeting Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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