Critical Vulnerability in Cisco WebEx Chrome Plugin
Update: Version 1.0.5 of the Google Chrome WebEx plugin, released this morning, fixes this issue.
The Google 0-Day project announced a critical remote code execution vulnerability in Cisco's WebEx plugin for Google Chrome. This vulnerability allows a remote attacker to execute arbitrary code on the victim's system by delivering it to the WebEx plugin via a special "secret" URL.
The secret pattern: cwcsf-nativemsg-iframe-43c85c0d-d633-af5e-c056-32dc7efc570b.html
Google set up a test page and published a detailed report about how this vulnerability can be used to execute code [1].
Note that version 1.0.3 of the plugin, which was released on Sunday (Jan 22nd), appears to be still vulnerable. At this point, it is probably best to uninstall the plugin and use a different browser for WebEx (of course, this issue may affect plugins for other browsers as well).
An attack would be invisible to the user if executed "right". The user does not have to willingly join a WebEx meeting to exploit this vulnerability.
[1] https://bugs.chromium.org/p/project-zero/issues/detail?id=1096
Application Security: Securing Web Apps, APIs, and Microservices | Online | US Eastern | Jan 27th - Feb 1st 2025 |
Comments
Anonymous
Jan 24th 2017
7 years ago
Anonymous
Jan 24th 2017
7 years ago
Anonymous
Jan 24th 2017
7 years ago
Issue also affects IE and Firefox per https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170124-webex
Mozilla are proactively disabling the extension in Firefox - https://bugzilla.mozilla.org/show_bug.cgi?id=1333225
Anonymous
Jan 25th 2017
7 years ago
"issue 1100 is a bypass that still allows code execution on 1.0.5. I have reported it to Cisco PSIRT. The issue requires some details that maybe considered new vulnerabilities, so the details are not available here until a patch is available."
Could someone please share info on how to disable this extension in a corporate environment? Must be open to re-enable once the new version is available. :)
EDIT: The information at https://www.chromium.org/administrators/policy-list-3#ExtensionInstallBlacklist can be used to achieve this.
But is there a nice write-up of "this is how we manage Chrome in our Corporate Environment that you can point me to? :)
Thanks
dotBATman
Anonymous
Jan 25th 2017
7 years ago
Anonymous
Jan 25th 2017
7 years ago
1) Obtain the Chrome ADMX template here: https://support.google.com/chrome/a/answer/187202?hl=en
2) Install the template: https://support.microsoft.com/en-us/help/929841/how-to-create-the-central-store-for-group-policy-administrative-template-files-in-windows-vista
3) Create a GPO and edit it
4) For Chrome: Computer Configuration > Policies > Admin Templates > Google > Google Chrome > Extensions > Configure extensions installation blacklist
4a) Set to Enabled
4b) In Show, add the value: jlhmfgmfgeifomenelglieieghnjghma
Note: this string is found from the URL of the Webex extension on Chrome web store.
5) For IE: Computer Configuration > Policies > Admin Templates >Windows Cmoponents > Internet Explorer > Security Features > Add-on Management > Add-on List
6a) Set to Enabled
6b) In Show, add the Value name: {E06E2E99-0AA1-11D4-ABA6-0060082AA75C}
6c) Set the Value to 0 (this forces disable)
Note: this value name is the Class Id of the Webex add-on "GpcContainer Class" by "Cisco Webex LLC".
See: https://technet.microsoft.com/en-us/itpro/internet-explorer/ie11-deploy-guide/enable-and-disable-add-ons-using-administrative-templates-and-group-policy?f=255&MSPPError=-2147217396
7) Save the GPO and link to the desired OUs. Allow time to propagate or use "gpupdate /force" to test right away.
NOTE: I only noticed the add-on in IE being disabled after closing and reopening IE.
Anonymous
Jan 25th 2017
7 years ago
Anonymous
Jan 26th 2017
7 years ago
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170124-webex
Anonymous
Jan 26th 2017
7 years ago
This is very useful - Let's hope people find and use this.
And it will of course work for other plug-ins as well! Just replace the ID.
Anonymous
Jan 29th 2017
7 years ago