CAPEC-26: Leveraging Race Conditions
Description
Extended Description
Applications often need to transform data in and out of serialized data formats, such as XML and YAML, by using a data parser. It may be possible for an adversary to inject data that may have an adverse effect on the parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the parser, an adversary can cause the parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to their advantage. DoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious data payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. 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 :
High
Type :
Meta
Relationships with other CAPECs
This table shows the other attack patterns and high level categories that are related to this attack pattern.
Prerequisites
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- A resource is accessed/modified concurrently by multiple processes such that a race condition exists.
- The adversary has the ability to modify the resource.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Medium Being able to "run the race" requires basic knowledge of concurrent processing including synchonization techniques.
Taxonomy mappings
Mappings to ATT&CK, OWASP and other frameworks.
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.
CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-363: Race Condition Enabling Link Following
CWE-366: Race Condition within a Thread
CWE-368: Context Switching Race Condition
CWE-370: Missing Check for Certificate Revocation after Initial Check
CWE-662: Improper Synchronization
CWE-665: Improper Initialization
CWE-667: Improper Locking
CWE-689: Permission Race Condition During Resource Copy
CWE-1223: Race Condition for Write-Once Attributes
CWE-1254: Incorrect Comparison Logic Granularity
CWE-1298: Hardware Logic Contains Race Conditions
Visit http://capec.mitre.org/ for more details.