CAPEC-523 Malicious Software Implanted

CAPEC ID: 523

CAPEC-523 Metadata

Likelihood of Attack

Low

Typical Severity

High

Overview

Summary

An attacker implants malicious software into the system in the supply chain distribution channel, with purpose of causing malicious disruption or allowing for additional compromise when the system is deployed.

Prerequisites

Physical access to the system after it has left the manufacturer but before it is deployed at the victim location.

Execution Flow

Step Phase Description Techniques
1 Explore [Determine Entry Point] The adversary must first identify a system that they wish to target and search for an entry point they can use to install the malicious software. This could be a system which they have prior knowledge of, giving them insight into the software and environment.
  • Use a JTAGulator to identify exposed JTAG and UART interfaces in smaller embedded systems.
  • Identify exposed USB connectors that could be used to load software.
2 Explore [Discover Vulnerability in Supply Chain] The adversary maps out the supply chain for the targeted system. They look for ooportunities to gain physical access to the system after it has left the manufacturer, but before it is deployed to the victim.
  • Procure a system and observe the steps it takes in the shipment process.
  • Identify possible warehouses that systems are stored after manufacturing.
3 Experiment [Test Malicious Software] Before performing the attack in the wild, an adversary will test the attack on a system they have procured to ensure that the desired outcome will be achieved.
  • Design malicious software that will give an adversary a backdoor into the system once it is deployed to the victim.
  • Obtain already designed malicious software that just need to be placed into the system.
4 Exploit [Implant Software in the Supply Chain] Using the vulnerability in the supply chain of the system discovered in the explore phase, the adversary implants the malicious software into the system. This results in the adversary gaining unintended access to systems once they reach the victim and can lead to a variety of follow up attacks.

Potential Solutions / Mitigations

Deploy strong code integrity policies to allow only authorized apps to run. Use endpoint detection and response solutions that can automaticalkly detect and remediate suspicious activities. Maintain a highly secure build and update infrastructure by immediately applying security patches for OS and software, implementing mandatory integrity controls to ensure only trusted tools run, and requiring multi-factor authentication for admins. Require SSL for update channels and implement certificate transparency based verification. Sign everything, including configuration files, XML files and packages. Develop an incident response process, disclose supply chain incidents and notify customers with accurate and timely information.

Related CAPECs

CAPEC ID Description
CAPEC-439 An attacker undermines the integrity of a product, software, or technology at some stage of the distribution channel. The core threat of modification or manipulation during distribution arise from the many stages of distribution, as a product may traverse multiple suppliers and integrators as the final asset is delivered. Components and services provided from a manufacturer to a supplier may be tampered with during integration or packaging.

Taxonomy Mappings

Taxonomy: ATTACK

Entry ID Entry Name
1195.002 Supply Chain Compromise: Compromise Software Supply Chain

Stay Ahead of Attack Patterns

Understanding CAPEC patterns helps security professionals anticipate and thwart potential attacks. Leverage these insights to enhance threat modeling, strengthen your software development lifecycle, and train your security teams effectively.