Dark Mode
Capec-682 Detail
Exploitation of Firmware or ROM Code with Unpatchable Vulnerabilities
Standard Software Hardware Likelihood: Medium Typical Severity: High
Parents: 212
Threats: T284 T389 T403
Tools: 11
An adversary may exploit vulnerable code (i.e., firmware or ROM) that is unpatchable. Unpatchable devices exist due to manufacturers intentionally or inadvertently designing devices incapable of updating their software. Additionally, with updatable devices, the manufacturer may decide not to support the device and stop making updates to their software.
When a vulnerability is found in a device that has no means of patching, the attack may be used against an entire class of devices. Devices from the same manufacturer often use similar or identical firmware, which could lead to widespread attacks. Devices of this nature are prime targets for botnet attacks. Consumer devices are frequently targeted for this attack due to the complexities of updating firmware once manufacturers no longer have physical access to a device. When exploiting a found vulnerability, adversaries often try to gain root access on a device. This allows them to use the device for any malicious purpose. Some example exploits are stealing device data, using the device for a ransomware attack, or recruiting the device for a botnet.
| External ID | Source | Link | Description |
|---|---|---|---|
| CAPEC-682 | capec | https://capec.mitre.org/data/definitions/682.html | |
| CWE-1277 | cwe | http://cwe.mitre.org/data/definitions/1277.html | |
| CWE-1310 | cwe | http://cwe.mitre.org/data/definitions/1310.html | |
| REF-723 | reference_from_CAPEC | https://www.computerweekly.com/news/252475324/Alarm-bells-ring-the-IoT-is-listening | Alex Scroxton, Alarm bells ring, the IoT is listening, 2019--12---13, TechTarget |
| REF-724 | reference_from_CAPEC | https://www.theregister.com/2019/12/11/f_secure_keywe/ | Matthew Hughes, Bad news: KeyWe Smart Lock is easily bypassed and can't be fixed, 2019--12---11, Situation Publishing |
| REF-725 | reference_from_CAPEC | https://krebsonsecurity.com/2020/03/zxyel-flaw-powers-new-mirai-iot-botnet-strain/ | Brian Krebs, Zyxel Flaw Powers New Mirai IoT Botnet Strain, 2020--03---20, Krebs on Security |
| REF-726 | reference_from_CAPEC | https://www.researchgate.net/publication/356065917_Digital_Age_Organizations_Uncovering_Over-the-Air_Updates_in_the_Smart_Product_Realm | Colin Schulz, Stefan Raff, Sebastian Kortmann, Nikolaus Obwegeser, Digital Age Organizations: Uncovering Over-the-Air Updates in the Smart Product Realm, 2021--12, International Conference on Information Systems (ICIS) 2021 |
Explore
-
Determine vulnerable firmware or ROM code: An adversary will attempt to find device models that are known to have unpatchable firmware or ROM code, or are deemed “end-of-support” where a patch will not be made. The adversary looks for vulnerabilities in firmware or ROM code for the identified devices, or looks for devices which have known vulnerabilities
| Techniques |
|---|
| Many botnets use wireless scanning to discover nearby devices that might have default credentials or commonly used passwords. Once these devices are infected, they can search for other nearby devices and so on. |
Experiment
-
Determine plan of attack: An adversary identifies a specific device/model that they wish to attack. They will also investigate similar devices to determine if the vulnerable firmware or ROM code is also present.
Exploit
-
Carry out attack: An adversary exploits the vulnerable firmware or ROM code on the identified device(s) to achieve their desired goal.
| Techniques |
|---|
| Install malware on a device to recruit it for a botnet. |
| Install malware on the device and use it for a ransomware attack. |
| Gain root access and steal information stored on the device. |
| Manipulate the device to behave in unexpected ways which would benefit the adversary. |
- Awareness of the hardware being leveraged.
- Access to the hardware being leveraged, either physically or remotely.
Not present
| High | Medium |
|---|---|
| Ability to identify physical entry points such as debug interfaces if the device is not being accessed remotely | |
| Knowledge of various wireless protocols to enable remote access to vulnerable devices |
| Integrity | Authorization | Access Control | Confidentiality |
|---|---|---|---|
| Modify Data | Gain Privileges | Gain Privileges | Read Data |
- An IoT company comes out with a line of smart products for home use such as home cameras, vacuums, and smart bulbs. The products become popular, and millions of consumers install these devices in their homes. All the devices use a custom module for encryption that is stored on a ROM chip, which is immutable memory and can't be changed. An adversary discovers that there is a vulnerability in the encryption module code that allows authentication bypass, gaining access to any device. The adversary then develops botnet code that is remotely downloaded onto the infected devices. This code scans the internet for nearby devices from the same product line and exploits the vulnerability, loading the botnet code onto these new devices. Over time, the adversary now has a botnet of devices that can carry out malicious activity such as a DDoS attacks. Once the vulnerability is found, it is impossible to remediate because the vulnerable code is unable to be updated.
- Older smartphones can become out of date and manufacturers may stop putting out security updates as they focus on newer models. If an adversary discovers a vulnerability in an old smartphone there is a chance that a security update will not be made to mitigate it. This leaves anyone using the old smartphone vulnerable.