|
|
|
|
| CAPEC-535: Malicious Gray Market Hardware |
 Description An attacker maliciously alters hardware components that will be sold on the gray market, allowing for victim disruption and compromise when the victim needs replacement hardware components for systems where the parts are no longer in regular supply from original suppliers, or where the hardware components from the attacker seems to be a great benefit from a cost perspective. Likelihood Of Attack Typical Severity Prerequisites
| Physical access to a gray market reseller's hardware components supply, or the ability to appear as a gray market reseller to the victim's buyer. |
Skills Required
[Level: High] Able to develop and manufacture malicious hardware components that perform the same functions and processes as their non-malicious counterparts. |
Mitigations
| Purchase only from authorized resellers. |
| Validate serial numbers from multiple sources |
Example Instances
| An attacker develops co-processor boards with malicious capabilities that are technically the same as a manufacturer's expensive upgrade to their flagship system. The victim has installed the manufacturer's base system without the expensive upgrade. The attacker contacts the victim and states they have the co-processor boards at a drastically-reduced price, falsely stating they were acquired from a bankruptcy liquidation of a company that had purchased them from the manufacturer. The victim after hearing the drastically reduced price decides to take advantage of the situation and purchases the upgrades from the attacker, and installs them. This allows the attacker to further compromise the victim. |
Taxonomy Mappings  CAPEC mappings to ATT&CK techniques leverage an inheritance model to streamline and minimize direct CAPEC/ATT&CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant ATT&CK mappings. Note that the ATT&CK Enterprise Framework does not use an inheritance model as part of the mapping to CAPEC.Relevant to the ATT&CK taxonomy mapping (see
parent
) References  Content History | Submissions |
|---|
| Submission Date | Submitter | Organization |
|---|
| 2014-06-23 (Version 2.6) | CAPEC Content Team | The MITRE Corporation | | | Modifications |
|---|
| Modification Date | Modifier | Organization |
|---|
| 2015-11-09 (Version 2.7) | CAPEC Content Team | The MITRE Corporation | | Updated Examples-Instances, Related_Attack_Patterns, Typical_Likelihood_of_Exploit | | 2022-02-22 (Version 3.7) | CAPEC Content Team | The MITRE Corporation | | Updated Mitigations |
More information is available — Please select a different filter.
|