# CVE-2019-1649: Cisco Secure Boot Hardware Tampering Vulnerability > An authenticated local attacker with elevated privileges can tamper with Secure Boot firmware, potentially installing malicious images or bricking the device. - **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 13 May 2019 - **Updated:** 20 Nov 2024 - **Also known as:** GHSA-8p3x-34c5-5pmx ## What is CVE-2019-1649? CVE-2019-1649 is a medium-severity vulnerability in Cisco Ios, published on 13 May 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A vulnerability in the logic that handles access control to one of the hardware components in Cisco's proprietary Secure Boot implementation could allow an authenticated, local attacker to write a modified firmware image to the component. This vulnerability affects multiple Cisco products that support hardware-based Secure Boot functionality. The vulnerability is due to an improper check on the area of code that manages on-premise updates to a Field Programmable Gate Array (FPGA) part of the Secure Boot hardware implementation. An attacker with elevated privileges and access to the underlying operating system that is running on the affected device could exploit this vulnerability by writing a modified firmware image to the FPGA. A successful exploit could either cause the device to become unusable (and require a hardware replacement) or allow tampering with the Secure Boot verification process, which under some circumstances may allow the attacker to install and boot a malicious software image. An attacker will need to fulfill all the following conditions to attempt to exploit this vulnerability: Have privileged administrative access to the device. Be able to access the underlying operating system running on the device; this can be achieved either by using a supported, documented mechanism or by exploiting another vulnerability that would provide an attacker with such access. Develop or have access to a platform-specific exploit. An attacker attempting to exploit this vulnerability across multiple affected platforms would need to research each one of those platforms and then develop a platform-specific exploit. Although the research process could be reused across different platforms, an exploit developed for a given hardware platform is unlikely to work on a different hardware platform. Weakness: CWE-667 (Improper Locking), CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2019-1649? It affects 27 products. Products: Cisco 15454-M-Wse-K9 Firmware, Cisco Analog Voice Network Interface Modules Firmware, Cisco Asa 5500 Firmware, Cisco Asr 1000 Series Firmware, Cisco Asr 1001 Firmware, Cisco Catalyst 9800-40 Wireless Controller Firmware, Cisco Catalyst 9800-80 Wireless Controller Firmware, Cisco Encs 5100 Firmware, Cisco Encs 5400 Firmware, Cisco Firepower 2100 Firmware, Cisco Firepower 4000 Firmware, Cisco Firepower 9000 Firmware, Cisco Ic3000-K9 Firmware, Cisco Industrial Security Appliances 3000 Firmware, Cisco Integrated Services Router 4200 Firmware, Cisco Integrated Services Router 4300 Firmware, Cisco Integrated Services Router 4400 Firmware, Cisco Integrated Services Router T1\/E1 Voice and Wan Network Interface Modules Firmware, Cisco Ios, Cisco Ios Xe and 7 more. ## How do I fix CVE-2019-1649? No fix has been published for CVE-2019-1649 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-1649 being exploited? There is no known exploitation of CVE-2019-1649 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1649 and fix it if it is affected. What it is: CVE-2019-1649 is a medium-severity vulnerability in Cisco Ios, published on 13 May 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-1649 in the wild and no public exploit code. Affected product: Cisco Ios. 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-1649/ (Markdown: https://insights.sbomify.com/CVE-2019-1649/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1649 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1649 - OSV: https://osv.dev/vulnerability/CVE-2019-1649 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1649/ Summaries are generated and may contain mistakes; the official description above is the record.