CVE-2017-3823
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 · uneditedAn issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Container before 106 on Mozilla Firefox, the GpcContainer Class ActiveX control plugin before 10031.6.2017.0126 on Internet Explorer, and the Download Manager ActiveX control plugin before 2.1.0.10 on Internet Explorer. A vulnerability in these Cisco WebEx browser extensions could allow an unauthenticated, remote attacker to execute arbitrary code with the privileges of the affected browser on an affected system. This vulnerability affects the browser extensions for Cisco WebEx Meetings Server and Cisco WebEx Centers (Meeting Center, Event Center, Training Center, and Support Center) when they are running on Microsoft Windows. The vulnerability is a design defect in an application programing interface (API) response parser within the extension. An attacker that can convince an affected user to visit an attacker-controlled web page or follow an attacker-supplied link with an affected browser could exploit the vulnerability. If successful, the attacker could execute arbitrary code with the privileges of the affected browser.
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 confidenceMultiple Cisco WebEx browser extensions (Chrome, Firefox, Internet Explorer) contain a design defect in their API response parser. This vulnerability allows unauthenticated remote attackers to execute arbitrary code with the privileges of the affected browser by tricking users into visiting attacker-controlled web pages.
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= 105= 2.1.0.9<= 10031.6.2017.0125<= 1.0.6= 2.0_base= 2.0_mr2= 2.0_mr3= 2.0_mr4= 2.0_mr5= 2.0_mr6= 2.0_mr7= 2.0_mr8= 2.0_mr9= 2.5_base= 2.5_mr1= 2.5_mr2= 2.6_base= 2.6_mr1= 2.6_mr2= 2.6_mr3= 2.7_base= 2.7_mr1= 2.7_mr2= t29_base= t30_base= t31_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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check Cisco WebEx Chrome extension versionOpen Chrome and navigate to chrome://extensions, enable Developer mode, find the WebEx extension, and note the version number. Alternatively, check the manifest.json file in the extension install directory (typically %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\)Affected if version is <= 1.0.6
-
Check Firefox ActiveTouch plugin versionIn Firefox, navigate to about:addons, click on Plugins, locate the Cisco WebEx ActiveTouch plugin, and note the version. Alternatively, check the plugin DLL file version in the Firefox plugins directoryAffected if version equals 105
-
Check IE GpcContainer Class COM registrationOpen Windows Registry Editor (regedit), navigate to HKEY_CLASSES_ROOT\CLSID\ and search for GpcContainer Class. Check the Version subkey value, or right-click the DLL and select Properties to view the File VersionAffected if version is <= 10031.6.2017.0125
-
Check Cisco Download Manager versionOpen Programs and Features (appwiz.cpl) or the Add/Remove Programs control panel, locate Cisco Download Manager, and note the version. Alternatively, right-click the download manager executable (typically in Program Files\Cisco\Cisco WebEx\Download Manager\) and view Properties > DetailsAffected if version equals 2.1.0.9
-
Verify browser extension is installed and activeFor each browser (Chrome, Firefox, IE), confirm the respective WebEx extension is present and enabled. In IE, also check Tools > Manage Add-ons to confirm GpcContainer Class is loadedAffected if any of the affected extensions are installed and enabled in the browser
You are affected if any Cisco WebEx browser extension (Chrome <=1.0.6, Firefox ActiveTouch =105, or IE GpcContainer <=10031.6.2017.0125) or Download Manager =2.1.0.9 is installed and active in your browsers.
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 dataUpdate Cisco WebEx browser extensions to the fixed versions: Chrome to 1.0.7, Firefox ActiveTouch plugin to 106, IE GpcContainer Class to 10031.6.2017.0126, and IE Download Manager to 2.1.0.10.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3823 — 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-3823 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