# CVE-2017-12337: Hardcoded credentials in Cisco Voice Operating System > Unauthenticated attackers can gain root access via a known password if an engineering flag remains enabled after specific upgrade procedures. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed - **Fix available:** No - **Published:** 16 Nov 2017 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-rg7v-73fx-2hfh ## What is CVE-2017-12337? CVE-2017-12337 is a critical vulnerability in Cisco Unified Communications Manager, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in the upgrade mechanism of Cisco collaboration products based on the Cisco Voice Operating System software platform could allow an unauthenticated, remote attacker to gain unauthorized, elevated access to an affected device. The vulnerability occurs when a refresh upgrade (RU) or Prime Collaboration Deployment (PCD) migration is performed on an affected device. When a refresh upgrade or PCD migration is completed successfully, an engineering flag remains enabled and could allow root access to the device with a known password. If the vulnerable device is subsequently upgraded using the standard upgrade method to an Engineering Special Release, service update, or a new major release of the affected product, this vulnerability is remediated by that action. Note: Engineering Special Releases that are installed as COP files, as opposed to the standard upgrade method, do not remediate this vulnerability. An attacker who can access an affected device over SFTP while it is in a vulnerable state could gain root access to the device. This access could allow the attacker to compromise the affected system completely. Cisco Bug IDs: CSCvg22923, CSCvg55112, CSCvg55128, CSCvg55145, CSCvg58619, CSCvg64453, CSCvg64456, CSCvg64464, CSCvg64475, CSCvg68797. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2017-12337? It affects 11 products. Products: Cisco Emergency Responder, Cisco Finesse, Cisco Hosted Collaboration Solution, Cisco Mediasense, Cisco Prime License Manager, Cisco Socialminer, Cisco Unified Communications Manager, Cisco Unified Communications Manager Im and Presence Service, Cisco Unified Contact Center Express, Cisco Unified Intelligence Center, Cisco Unity Connection. ## How do I fix CVE-2017-12337? No fix has been published for CVE-2017-12337 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-12337 being exploited? There is no known exploitation of CVE-2017-12337 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Unified Communications Manager - [CVE-2008-1154](https://insights.sbomify.com/CVE-2008-1154/): Auth bypass in n/a (critical 10.0) - [CVE-2023-20101](https://insights.sbomify.com/CVE-2023-20101/): Hardcoded credentials in Cisco Emergency Responder (critical 9.8) - [CVE-2016-6468](https://insights.sbomify.com/CVE-2016-6468/): Cross-site request forgery in Cisco Emergency Responder (high 8.8) - [CVE-2023-20259](https://insights.sbomify.com/CVE-2023-20259/): Denial of service in Cisco Emergency Responder (high 8.6) - [CVE-2017-6779](https://insights.sbomify.com/CVE-2017-6779/): Denial of service in Multiple Cisco Products unknown (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-12337 and fix it if it is affected. What it is: CVE-2017-12337 is a critical vulnerability in Cisco Unified Communications Manager, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-12337 in the wild and no public exploit code. Affected product: Cisco Unified Communications Manager. 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-12337/ (Markdown: https://insights.sbomify.com/CVE-2017-12337/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-12337 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-12337 - OSV: https://osv.dev/vulnerability/CVE-2017-12337 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-12337/ Summaries are generated and may contain mistakes; the official description above is the record.