# CVE-2017-12287: Denial of service in Cisco Expressway Series and Cisco TelePresence Video Communication Server > An authenticated remote attacker can cause a temporary denial of service by sending a crafted URL to the REST API. - **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 19 Oct 2017 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-pcx4-96gw-4344 ## What is CVE-2017-12287? CVE-2017-12287 is a medium-severity denial of service vulnerability in Cisco Expressway Series and Cisco TelePresence Video Communication Server, published on 19 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A vulnerability in the cluster database (CDB) management component of Cisco Expressway Series Software and Cisco TelePresence Video Communication Server (VCS) Software could allow an authenticated, remote attacker to cause the CDB process on an affected system to restart unexpectedly, resulting in a temporary denial of service (DoS) condition. The vulnerability is due to incomplete input validation of URL requests by the REST API of the affected software. An attacker could exploit this vulnerability by sending a crafted URL to the REST API of the affected software on an affected system. A successful exploit could allow the attacker to cause the CDB process on the affected system to restart unexpectedly, resulting in a temporary DoS condition. Cisco Bug IDs: CSCve77571. Weakness: CWE-20 (Improper Input Validation), CWE-399 ## Which versions are affected by CVE-2017-12287? It affects 3 products. Products: Cisco Expressway, Cisco Telepresence Conductor, Cisco Telepresence Video Communication Server. ## How do I fix CVE-2017-12287? No fix has been published for CVE-2017-12287 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-12287 being exploited? There is no known exploitation of CVE-2017-12287 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Expressway Series and Cisco TelePresence Video Communication Server - [CVE-2024-20252](https://insights.sbomify.com/CVE-2024-20252/): Cross-site request forgery in Cisco TelePresence Video Communication Server (VCS) Expressway (critical 9.6) - [CVE-2024-20254](https://insights.sbomify.com/CVE-2024-20254/): Cross-site request forgery in Cisco TelePresence Video Communication Server (VCS) Expressway (critical 9.6) - [CVE-2022-20812](https://insights.sbomify.com/CVE-2022-20812/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0) - [CVE-2022-20813](https://insights.sbomify.com/CVE-2022-20813/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0) - [CVE-2017-3790](https://insights.sbomify.com/CVE-2017-3790/): Denial of service in Cisco Expressway Series Software and Cisco TelePresence VCS Software All versions prior to version X8.8.2 are vulnerable (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-12287 and fix it if it is affected. What it is: CVE-2017-12287 is a medium-severity denial of service vulnerability in Cisco Expressway Series and Cisco TelePresence Video Communication Server, published on 19 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-12287 in the wild and no public exploit code. Affected product: Cisco Expressway Series and Cisco TelePresence Video Communication Server. 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-12287/ (Markdown: https://insights.sbomify.com/CVE-2017-12287/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-12287 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-12287 - OSV: https://osv.dev/vulnerability/CVE-2017-12287 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-12287/ Summaries are generated and may contain mistakes; the official description above is the record.