CAPEC-537: Infiltration of Hardware Development Environment

Description
An adversary, leveraging the ability to manipulate components of primary support systems and tools within the development and production environments, inserts malicious software within the hardware and/or firmware development environment. The infiltration purpose is to alter developed hardware components in a system destined for deployment at the victim's organization, for the purpose of disruption or further compromise.
Extended Description

XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.

Severity :

High

Possibility :

Low

Type :

Detailed
Relationships with other CAPECs

This table shows the other attack patterns and high level categories that are related to this attack pattern.

CAPEC-444: Development Alteration Development Alteration
Prerequisites

This table shows the other attack patterns and high level categories that are related to this attack pattern.

  • The victim must use email or removable media from systems running the IDE (or systems adjacent to the IDE systems).
  • The victim must have a system running exploitable applications and/or a vulnerable configuration to allow for initial infiltration.
  • The adversary must have working knowledge of some if not all of the components involved in the IDE system as well as the infrastructure.
Skills required

This table shows the other attack patterns and high level categories that are related to this attack pattern.

  • Medium Intelligence about the manufacturer's operating environment and infrastructure.
  • High Ability to develop, deploy, and maintain a stealth malicious backdoor program remotely in what is essentially a hostile environment.
  • High Development skills to construct malicious attachments that can be used to exploit vulnerabilities in typical desktop applications or system configurations. The malicious attachments should be crafted well enough to bypass typical defensive systems (IDS, anti-virus, etc)
Taxonomy mappings

Mappings to ATT&CK, OWASP and other frameworks.

ATTACK | Supply Chain Compromise: Compromise Hardware Supply Chain
Related CWE

A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful.

Visit http://capec.mitre.org/ for more details.