COMMON ATTACK PATTERN ENUMERATION AND CLASSIFICATIONLive MITRE record

CAPEC-74

Manipulating State

The adversary modifies state information maintained by the target software or causes a state transition in hardware. If successful, the target will use this tainted state and execute in an unintended manner. State management is an important function within a software application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits. If there is a hardware logic error in a finite state machine, the adversary can use this to put the system in an undefined state which could cause a denial of service or exposure of secure data.

Abstraction

Meta

Typical severity

High

Likelihood of attack

Medium

Understand the attack

What is this attack pattern?

The adversary modifies state information maintained by the target software or causes a state transition in hardware. If successful, the target will use this tainted state and execute in an unintended manner. State management is an important function within a software application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits. If there is a hardware logic error in a finite state machine, the adversary can use this to put the system in an undefined state which could cause a denial of service or exposure of secure data.

Execution flow

How does the attack proceed, step by step?

1

Explore

Attack step

Adversary determines the nature of state management employed by the target. This includes determining the location (client-side, server-side or both applications) and possibly the items stored as part of user state.
2

Experiment

Attack step

The adversary now tries to modify the user state contents (possibly indiscriminately if the contents are encrypted or otherwise obfuscated) or cause a state transition and observe the effects of this change on the target.
3

Exploit

Attack step

Having determined how to manipulate the state, the adversary can perform illegitimate actions.

Requirements

What does the attack require?

Prerequisites

  • User state is maintained at least in some way in user-controllable locations, such as cookies or URL parameters.
  • There is a faulty finite state machine in the hardware logic that can be exploited.

Skills required

  • Medium: The adversary needs to have knowledge of state management as employed by the target application, and also the ability to manipulate the state in a meaningful way.

Resources required

  • The adversary needs a data tampering tool capable of generating and creating custom inputs to aid in the attack, like Fiddler, Wireshark, or a similar in-browser plugin (e.g., Tamper Data for Firefox).

Impact

What does a successful attack lead to?

Gain Privileges

Affected scopes: Confidentiality, Access Control, Authorization

Modify Data

Affected scopes: Integrity

Unreliable Execution

Affected scopes: Availability

Defence

How is it prevented and mitigated?

1
Do not rely solely on user-controllable locations, such as cookies or URL parameters, to maintain user state.
2
Avoid sensitive information, such as usernames or authentication and authorization information, in user-controllable locations.
3
Sensitive information that is part of the user state must be appropriately protected to ensure confidentiality and integrity at each request.
4
All possible states must be handled by hardware finite state machines.

Real world

MITRE example instances

Example instance 1Detail
During the authentication process, an application stores the authentication decision (auth=0/1) in unencrypted cookies. At every request, this cookie is checked to permit or deny a request. An adversary can easily violate this representation of user state and set auth=1 at every request in order to gain illegitimate access and elevated privilege in the application.
CAPEC-74: Manipulating State — DayBreach Saldırı Sözlüğü · DayBreach