Home > CAPEC List > CAPEC-536: Data Injected During Configuration (Version 2.9)  

CAPEC-536: Data Injected During Configuration

 
Data Injected During Configuration
Definition in a New Window Definition in a New Window
Attack Pattern ID: 536
Abstraction: Detailed
Status: Draft
Completeness: Stub
Presentation Filter:
+ Summary

An attacker with access to data files and processes on a victim's system injects false data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the attacker.

+ Attack Prerequisites
  • The attacker must have previously compromised the victim's systems or have physical access to the victim's systems.

  • Advanced knowledge of software and hardware capabilities of a manufacturer's product.

+ Typical Severity

High

+ Typical Likelihood of Exploit

Likelihood: Low

The nature of these type of attacks involve a coordinated effort between well-funded multiple attackers, and sometimes require physical access to successfully complete an attack. As a result these types of attacks are not launched on a large scale against any potential victim, but are typically highly targeted against victims who are often targeted and may have rather sophisticated cyber defenses already in place.

+ Examples-Instances

Description

An attacker wishes to bypass a security system to access an additional network segment where critical data is kept. The attacker knows that some configurations of the security system will allow for remote bypass under certain conditions, such as switching a specific parameter to a different value. The attacker knows the bypass will work but also will be detected within the logging data of the security system. The attacker waits until an upgrade is performed to the security system by the victim's system administrators, and the attacker has access to an external logging system. The attacker injects false log entries that cause the administrators to think there are two different error states within the security system - one involving the specific parameter and the other involving the logging entries. The specific parameter is adjusted to a different value, and the logging level is reduced to a lower level that will not cause an attacker bypass to be detected. The attacker stops injecting false log data, and the administrators of the security system believe the issues were caused by the upgrade and are now resolved. The attacker is then able to bypass the security system.

+ Attacker Skills or Knowledge Required

Skill or Knowledge Level: High

Ability to generate and inject false data into operational data into a system with the intent of causing the victim to alter the configuration of the system.

+ References
[R.536.1] [REF-50] John F. Miller. "Supply Chain Attack Framework and Attack Patterns". The MITRE Corporation. 2013. <http://www.mitre.org/sites/default/files/publications/supply-chain-attack-framework-14-0228.pdf>.
+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
Modifications
ModifierOrganizationDateCommentsSource
CAPEC Content TeamThe MITRE Corporation2015-11-09Updated Related_Attack_PatternsInternal
CAPEC Content TeamThe MITRE Corporation2017-01-09Updated Examples-Instances, Typical_Likelihood_of_ExploitInternal

More information is available — Please select a different filter.
Page Last Updated or Reviewed: December 07, 2015