CVE-2019-1649

Cisco Secure Boot Hardware Tampering Vulnerability

MEDIUM
6.7
CVSS Score
Published: May 13, 2019 at 07:10 PM UTC
Updated: June 17, 2026 at 02:28 AM UTC
193 products affected across 1 vendorIOSIOS XeNx OS

Using Cisco Routers by Cisco?

Get instant alerts when new vulnerabilities affect Cisco Routers - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.7
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 11.1
Affected range stops below 11.1, so it looks safe — our inference, not a vendor statement
cisco-15454-m-wse-k9 (same device)
All versions
cisco-nim-2bri-nt-te (environment) · cisco-nim-2fox (environment) · cisco-nim-2fxs (environment) · cisco-nim-2fxs-4fxo (environment) · cisco-nim-2fxs-4fxop (environment) · cisco-nim-2fxsp (environment) · cisco-nim-4bri-nt-te (environment) · cisco-nim-4e-m (environment) · cisco-nim-4fxo (environment) · cisco-nim-4fxs (environment) · cisco-nim-4fxsp (environment)
v < 1.1.15
Affected range stops below 1.1.15, so it looks safe — our inference, not a vendor statement
cisco-asa-5506-x (environment) · cisco-asa-5506h-x (environment) · cisco-asa-5506w-x (environment) · cisco-asa-5508-x (environment) · cisco-asa-5516-x (environment)
All versions
cisco-asr-1000-esp100 (environment) · cisco-asr1000-2t-20x1ge (environment) · cisco-asr1000-6tge (environment) · cisco-asr1000-esp200 (environment) · cisco-asr1000-mip100 (environment) · cisco-asr1000-rp3 (environment) · cisco-asr-1000-series (same device)
cisco-asr-1002-hx (environment) · cisco-asr-1001-hx (same device) · cisco-asr-1001-x (same device)
All versions
cisco-catalyst-9800-40-wireless-controller (same device)
All versions
cisco-catalyst-9800-80-wireless-controller (same device)
All versions
cisco-encs-5100 (same device)
All versions
cisco-encs-5400 (same device)
v < 2.6.1.134
Affected range stops below 2.6.1.134, so it looks safe — our inference, not a vendor statement
cisco-firepower-2110 (environment) · cisco-firepower-2120 (environment) · cisco-firepower-2130 (environment) · cisco-firepower-2140 (environment)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/108350
Third Party Advisoryx_refsource_CERT-VNUS Government Resource
https://www.kb.cert.org/vuls/id/400865
x_refsource_MISCThird Party AdvisoryUS Government Resource
https://www.us-cert.gov/ics/advisories/icsa-20-072-03

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-284CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card