What is CVE-2019-1649?A medium-severity flaw in ASA 5500 Firmware, explained.
CVE-2019-1649 is a medium-severity flaw (CVSS 6.7) in ASA 5500 Firmware from Cisco, published on 13 May 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.6%. If you run an affected version, plan in the vendor’s fix.
Published 13 May 2019. Record last updated 13 December 2022. We keep this page's data up to date.
What is CVE-2019-1649? In plain terms.
An attacker has to be already on the device with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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.
What kind of flaw is it?
- CWE-284Improper Access Control
- CWE-667Improper Locking
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn administrator account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Is CVE-2019-1649 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.6%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2019-1649 scores 21. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-1649 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-1649? 193 products.
The published record lists 193 products from 1 vendor. Versions are shown as published: "before 1.1.15" means every version up to, but not including, 1.1.15. If you run one of these, check your version, then go to the fix below.
- Operating system
ASA 5500 Firmware
by Cisco
Affected versionsbefore 1.1.15 - Operating system
IOS XE
by Cisco
Affected versionsbefore 16.12.1before 16.3.9before 16.2.1before 15.5(1)sy4before 16.9.416.4.0 to before 16.6.7 - Operating system
IOS
by Cisco
Affected versionsbefore 15.6(3)m7before 15.6(3)m6b15.7 to 15.7(3)m515.8 to before 15.8(3)m315.9 to before 15.9(3)m - Operating system
IOS XR
by Cisco
Affected versions7.0.17.1.1 - Operating system
NX-OS
by Cisco
Affected versionsbefore 8.4.1before 9.3(2) - Hardware
1120 Connected Grid Router
by Cisco
Affected versionsversion not specified - Hardware
1240 Connected Grid Router
by Cisco
Affected versionsversion not specified - Hardware
15454-M-Wse-K9
by Cisco
Affected versionsversion not specified - Operating system
15454-M-Wse-K9 Firmware
by Cisco
Affected versionsbefore 11.1
How do I fix CVE-2019-1649? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2019-1649 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 a...
- Matched to
- ASA 5500 Firmware on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-1649 is a medium-severity flaw in ASA 5500 Firmware from Cisco, published on 13 May 2019. An attacker has to be already on the device with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 6.7 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2019-1649 is 21 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.6%. That can change at any time, which is why we keep watching.
For ASA 5500 Firmware from Cisco: before 1.1.15. The record lists 193 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.