Permanent boot failure via ROMMON boot-ROM corruption
Published Apr 15, 2022 · Updated Nov 6, 2024
Boot-loader flaw in Cisco IOS ROMMON Software 15.2(7r)E2 allows physically proximate attackers to cause permanent boot failure. The development boot loader exposes ROMMON commands that can irrecoverably corrupt the boot ROM. Physical access is required to reboot the device, interrupt the boot cycle, and issue the commands; the device continues operating until its next reload or power cycle.
Summary
What happened
Boot-loader flaw in Cisco IOS ROMMON Software 15.2(7r)E2 allows physically proximate attackers to cause permanent boot failure. The development boot loader exposes ROMMON commands that can irrecoverably corrupt the boot ROM. Physical access is required to reboot the device, interrupt the boot cycle, and issue the commands; the device continues operating until its next reload or power cycle.
The record
- CVE
- CVE-2022-20661
- Published
- Apr 15, 2022
- Updated
- Nov 6, 2024
- Vendor
- ClamAV
- Product
- Cisco IOS ROMMON Software
- Classifications
- CWE-489, T1495
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2022CVE publishedPublication date reported by the CVE source.
- Nov 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo