# CVE-2017-6753: Code injection in Cisco WebEx Browser Extension

> Remote attackers can execute arbitrary code via malicious links in Cisco WebEx browser extensions on Windows.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j6hm-qxwv-3jwr

## What is CVE-2017-6753?

CVE-2017-6753 is a high-severity code injection vulnerability in Cisco Webex Meetings, published on 25 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in Cisco WebEx browser extensions for Google Chrome and Mozilla Firefox 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, Cisco WebEx Centers (Meeting Center, Event Center, Training Center, and Support Center), and Cisco WebEx Meetings when they are running on Microsoft Windows. The vulnerability is due to a design defect in the extension. An attacker who 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. The following versions of the Cisco WebEx browser extensions are affected: Versions prior to 1.0.12 of the Cisco WebEx extension on Google Chrome, Versions prior to 1.0.12 of the Cisco WebEx extension on Mozilla Firefox. Cisco Bug IDs: CSCvf15012 CSCvf15020 CSCvf15030 CSCvf15033 CSCvf15036 CSCvf15037.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-6753?

It affects 20 products.


Products: Cisco Webex Event Center, Cisco Webex Meeting Center, Cisco Webex Meetings, Cisco Webex Meetings Server, Cisco Webex Meetings Server 2.0, Cisco Webex Meetings Server 2.0 Mr8 Patch, Cisco Webex Meetings Server 2.0 Mr9 Patch, Cisco Webex Meetings Server 2.5, Cisco Webex Meetings Server 2.5 Mr2 Patch, Cisco Webex Meetings Server 2.5 Mr5 Patch, Cisco Webex Meetings Server 2.5 Mr6 Patch, Cisco Webex Meetings Server 2.6, Cisco Webex Meetings Server 2.6 Mr1 Patch, Cisco Webex Meetings Server 2.6 Mr2 Patch, Cisco Webex Meetings Server 2.6 Mr3 Patch, Cisco Webex Meetings Server 2.7, Cisco Webex Meetings Server 2.7 Mr1 Patch, Cisco Webex Meetings Server 2.7 Mr2 Patch, Cisco Webex Support Center, Cisco Webex Training Center.

## How do I fix CVE-2017-6753?

No fix has been published for CVE-2017-6753 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6753 being exploited?

There is no known exploitation of CVE-2017-6753 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2019-15987](https://insights.sbomify.com/CVE-2019-15987/): Cisco WebEx Centers Username Enumeration Information Disclosure Vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6753 and fix it if it is affected.

What it is: CVE-2017-6753 is a high-severity code injection vulnerability in Cisco Webex Meetings, published on 25 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6753 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6753/ (Markdown: https://insights.sbomify.com/CVE-2017-6753/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6753
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6753
- OSV: https://osv.dev/vulnerability/CVE-2017-6753

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6753/
Summaries are generated and may contain mistakes; the official description above is the record.