# CVE-2019-12636: Cisco Small Business Smart and Managed Switches Cross-Site Request Forgery Vulnerability > An attacker can trick an admin into clicking a link to perform arbitrary actions, potentially altering configuration or causing denial of service. - **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 16 Oct 2019 - **Updated:** 21 Nov 2024 - **Also known as:** GHSA-33c2-986r-8vm4 ## What is CVE-2019-12636? CVE-2019-12636 is a high-severity vulnerability in Cisco Small Business 250 Series Smart Switches Software, published on 16 Oct 2019. 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 the web-based management interface of Cisco Small Business Smart and Managed Switches could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections for the web-based management interface on an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the targeted user. If the user has administrative privileges, the attacker could alter the configuration, execute commands, or cause a denial of service (DoS) condition on an affected device. Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2019-12636? It affects 108 products. Products: Cisco Sf200-24 Firmware, Cisco Sf200-24fp Firmware, Cisco Sf200-24p Firmware, Cisco Sf200-48 Firmware, Cisco Sf200-48p Firmware, Cisco Sf200e-24 Firmware, Cisco Sf200e-24p Firmware, Cisco Sf200e-48 Firmware, Cisco Sf200e48p Firmware, Cisco Sf250-08 Firmware, Cisco Sf250-08hp Firmware, Cisco Sf250-10p Firmware, Cisco Sf250-18 Firmware, Cisco Sf250-24 Firmware, Cisco Sf250-24p Firmware, Cisco Sf250-26 Firmware, Cisco Sf250-26hp Firmware, Cisco Sf250-26p Firmware, Cisco Sf250-48 Firmware, Cisco Sf250-48hp Firmware and 88 more. ## How do I fix CVE-2019-12636? No fix has been published for CVE-2019-12636 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-12636 being exploited? There is no known exploitation of CVE-2019-12636 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Small Business 250 Series Smart Switches Software - [CVE-2018-15439](https://insights.sbomify.com/CVE-2018-15439/): Cisco Small Business Switches Privileged Access Vulnerability (critical 9.8) - [CVE-2020-3363](https://insights.sbomify.com/CVE-2020-3363/): Cisco Small Business Smart and Managed Switches Denial of Service Vulnerability (high 8.6) - [CVE-2020-3297](https://insights.sbomify.com/CVE-2020-3297/): Cisco Small Business Smart and Managed Switches Session Management Vulnerability (high 8.1) - [CVE-2019-15993](https://insights.sbomify.com/CVE-2019-15993/): Cisco Small Business Switches Information Disclosure Vulnerability (high 7.5) - [CVE-2019-1859](https://insights.sbomify.com/CVE-2019-1859/): Cisco Small Business Switches Secure Shell Certificate Authentication Bypass Vulnerability (high 7.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-12636 and fix it if it is affected. What it is: CVE-2019-12636 is a high-severity vulnerability in Cisco Small Business 250 Series Smart Switches Software, published on 16 Oct 2019. 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-2019-12636 in the wild and no public exploit code. Affected product: Cisco Small Business 250 Series Smart Switches Software. 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-2019-12636/ (Markdown: https://insights.sbomify.com/CVE-2019-12636/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12636 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12636 - OSV: https://osv.dev/vulnerability/CVE-2019-12636 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-12636/ Summaries are generated and may contain mistakes; the official description above is the record.