Webex Meeting CenterApplication · Cisco
CVE-2017-3799
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 a URL parameter of Cisco WebEx Meeting Center could allow an unauthenticated, remote attacker to perform site redirection. More Information: CSCzu78401. Known Affected Releases: T28.1.
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 confidenceAn open redirect vulnerability in the URL parameter handling of Cisco WebEx Meeting Center allows an unauthenticated remote attacker to manipulate the parameter to redirect users to arbitrary external websites. This is a classic open redirect flaw where the application fails to validate or sanitize the redirect URL parameter before using it.
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
= wbs28_baseCVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 WebEx Meeting Center versionLocate the installed version of Cisco WebEx Meeting Center in the system documentation, control panel, or version information file. Common locations include the admin interface or installation logs.Affected if The installed version is wbs28_base exactly, as this is the only version listed as affected by this CVE.
-
Verify URL redirect functionality existsAccess the WebEx Meeting Center login or navigation page and identify any URL parameters that control redirection, such as parameters named 'url', 'redirect', 'return', 'next', or similar. Look for functionality that redirects users after authentication or certain actions.Affected if The application uses a URL parameter to handle redirects and that parameter accepts full URLs (http/https) or external domains.
-
Test redirect parameter for validationModify the suspected redirect parameter in a WebEx URL to point to an external domain (e.g., add '&url=http://example.com' to the URL). Submit the modified URL and observe whether the application redirects to the external site without validation warnings or blocks.Affected if The application accepts and follows redirects to arbitrary external domains without validating that the URL is relative or from an approved allowlist.
-
Check admin configuration for redirect rulesExamine the WebEx Meeting Center admin settings or configuration files for any defined redirect validation rules, trusted domains lists, or URL allowlist settings.Affected if No redirect validation rules exist or the configuration explicitly permits external URL redirects.
You are affected if your installed WebEx Meeting Center version is wbs28_base AND the application contains URL redirect functionality that accepts external URLs without validation.
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 referenced in CSCzu78401 for the T28.1 release. As an interim measure, implement URL validation to ensure redirect parameters only allow trusted, relative paths or explicitly approved domains.
Fix this in Webex Meeting Center
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3799 — 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-2017-3799 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