Webex Meetings ServerApplication · Cisco
CVE-2014-3301
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 ProfileAction controller in Cisco WebEx Meetings Server (CWMS) 1.5(.1.131) and earlier allows remote attackers to obtain sensitive information by reading stack traces in returned messages, aka Bug ID CSCuj81700.
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 ProfileAction controller in Cisco WebEx Meetings Server (CWMS) 1.5 and earlier returns detailed stack traces in error responses, exposing sensitive internal information such as file paths, class names, method names, and potentially system configuration details to remote attackers.
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
<= 1.5\(.1.131\)= 1.5= 1.5\(.1.6\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco WebEx Meetings Server versionAccess the administrative interface or check system documentation to determine the installed CWMS version. Look for version indicators in the about page, server headers, or admin panel.Affected if The installed version is 1.5, 1.5(.1.6), or any version <= 1.5(.1.131)
-
Locate the ProfileAction controller endpointIdentify the URL path for the ProfileAction controller. This is typically found in the WebEx meetings application web interface under user profile or account settings.Affected if The ProfileAction controller is accessible and enabled on the server
-
Trigger an error condition on the ProfileAction endpointSend a crafted request to the ProfileAction endpoint with malformed input, missing required parameters, or an invalid session to provoke an error response.Affected if The server returns an HTTP error response (4xx or 5xx) to the request
-
Inspect error response for stack trace disclosureExamine the full HTTP response body from the error condition. Look for Java stack traces, file paths (such as /opt or C:\ paths), class names, method names, and system configuration details.Affected if The error response contains detailed stack traces with file paths, class names, or method names
A user is affected if running Cisco WebEx Meetings Server version 1.5 or earlier and error responses from the ProfileAction controller expose stack traces containing sensitive internal information.
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 dataApply the vendor patch or upgrade to a Cisco WebEx Meetings Server version beyond 1.5(.1.131) that addresses this information disclosure vulnerability.
Fix this in Webex Meetings Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3301 — 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-2014-3301 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