Webex Meetings ServerApplication · Cisco
CVE-2013-1231
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 HTTP implementation in Cisco WebEx Node for MCS and WebEx Meetings Server allows remote attackers to read cache files via a crafted request, aka Bug IDs CSCue36664 and CSCue36629.
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 confidenceA path traversal vulnerability in the HTTP implementation of Cisco WebEx Node for MCS and WebEx Meetings Server allows remote attackers to read arbitrary cache files via specially crafted HTTP requests. The vulnerability stems from insufficient input validation in the HTTP request handling, enabling directory traversal sequences to access files outside the intended cache directory.
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
all versions
Webex Node For McsApplication
all versionsCVSS 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 product installationCheck for presence of Cisco WebEx Meetings Server or WebEx Node for MCS by searching for typical installation directories (e.g., /opt/webex, C:\Program Files\WebEx) or by querying running processes for webex-related executablesAffected if Either Cisco WebEx Meetings Server or Cisco WebEx Node for MCS is installed on the system
-
Verify HTTP service is enabledCheck if the WebEx HTTP service (typically port 80/443 or known WebEx ports like 8080, 8443) is listening and accessible on the affected system using netstat or similar network toolsAffected if The WebEx HTTP service is running and accepting connections
-
Confirm network exposureDetermine if the HTTP interface is accessible from network segments outside the trusted internal network by reviewing firewall rules, ACLs, or by attempting a curl/wget request to the service from an untrusted network perspectiveAffected if The WebEx HTTP service is reachable from untrusted network segments (not just localhost or management VLAN)
If Cisco WebEx Meetings Server or WebEx Node for MCS is installed with its HTTP service exposed to any network access, the environment is affected by CVE-2013-1231 since all versions contain the path traversal vulnerability.
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 Cisco patches for bug IDs CSCue36664 and CSCue36629, or upgrade to a patched version of Cisco WebEx Node for MCS and WebEx Meetings Server. If patches are unavailable, consider restricting HTTP access to the WebEx services via network segmentation or firewall rules.
Fix this in Webex Meetings Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1231 — 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-2013-1231 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