Webex Meetings ServerApplication · Cisco
CVE-2018-0108
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 · uneditedA vulnerability in Cisco WebEx Meetings Server could allow an unauthenticated, remote attacker to collect customer files via an out-of-band XML External Entity (XXE) injection. An attacker could exploit this vulnerability to gain information to conduct additional reconnaissance attacks. The vulnerability is due to the ability of an attacker to perform an out-of-band XXE injection on the system, which could allow an attacker to capture customer files and redirect them to another destination address. An exploit could allow the attacker to discover sensitive customer data. Cisco Bug IDs: CSCvg36996.
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 confidenceCVE-2018-0108 is an out-of-band XML External Entity (XXE) injection vulnerability in Cisco WebEx Meetings Server. An unauthenticated remote attacker can exploit this by sending specially crafted XML requests containing malicious external entity definitions that cause the server to fetch and exfiltrate customer files to an attacker-controlled destination. This enables reconnaissance and sensitive data disclosure without authentication.
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 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 presenceReview installed software inventory or running services on the system for 'Cisco WebEx Meetings Server' or 'WebEx' components. Check for processes named 'webex' or services related to Cisco WebEx.Affected if The system runs Cisco WebEx Meetings Server - all versions are affected by CVE-2018-0108.
-
Confirm XML processing is enabledExamine the WebEx Meetings Server configuration files and XML parser settings. Look for XML handling modules or handlers that process incoming XML requests.Affected if XML processing is active and external entity resolution is not explicitly disabled in the XML parser configuration.
-
Check for unauthenticated XML endpointsReview WebEx server logs and network access controls for unauthenticated XML request endpoints. These endpoints accept XML input without prior authentication.Affected if The server exposes unauthenticated XML request endpoints that accept external entity definitions.
-
Inspect outbound network connectionsMonitor or review WebEx server network connections for outbound requests to untrusted or attacker-controlled IP addresses or domains, particularly those originating from XML parser operations.Affected if Unexpected outbound HTTP/FTP requests from the WebEx server to unknown external destinations are observed in logs or network traffic.
If Cisco WebEx Meetings Server is running with unauthenticated XML endpoints and external entity processing enabled, the server is vulnerable to CVE-2018-0108 XXE injection attacks.
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 Cisco patch for CSCvg36996 and disable external entity processing in XML parsers used by the WebEx Meetings Server to prevent XXE attacks.
Fix this in Webex Meetings Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0108 — 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-2018-0108 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