Home > CAPEC List > CAPEC-110: SQL Injection through SOAP Parameter Tampering (Version 2.11)  

CAPEC-110: SQL Injection through SOAP Parameter Tampering

SQL Injection through SOAP Parameter Tampering
Definition in a New Window Definition in a New Window
Attack Pattern ID: 110
Abstraction: Detailed
Status: Draft
Completeness: Complete
Presentation Filter:
+ Summary

An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.

+ Attack Steps
  1. Detect Incorrect SOAP Parameter Handling: The attacker tampers with the SOAP message parameters and looks for indications that the tampering caused a change in behavior of the targeted application.

    The attacker tampers with the SOAP message parameters by injecting some special characters such as single quotes, double quotes, semi columns, etc. The attacker observes system behavior.

  1. Probe for SQL Injection vulnerability: The attacker injects SQL syntax into vulnerable SOAP parameters identified during the Explore phase to search for unfiltered execution of the SQL syntax in a query.

  1. Inject SQL via SOAP Parameters: The attacker injects SQL via SOAP parameters identified as vulnerable during Explore phase to launch a first or second order SQL injection attack.

    An attacker performs a SQL injection attack via the usual methods leveraging SOAP parameters as the injection vector. An attacker has to be careful not to break the XML parser at the service provider which may prevent the payload getting through to the SQL query. The attacker may also look at the WSDL for the web service (if available) to better understand what is expected by the service provider.

+ Attack Prerequisites
  • SOAP messages are used as a communication mechanism in the system

  • SOAP parameters are not properly validated at the service provider

  • The service provider does not properly utilize parameter binding when building SQL queries

+ Typical Severity

Very High

+ Typical Likelihood of Exploit

Likelihood: High

+ Methods of Attack
  • Injection
  • Analysis
+ Examples-Instances


An attacker uses a travel booking system that leverages SOAP communication between the client and the travel booking service. An attacker begins to tamper with the outgoing SOAP messages by modifying their parameters to include characters that would break a dynamically constructed SQL query. He notices that the system fails to respond when these malicious inputs are injected in certain parameters transferred in a SOAP message. The attacker crafts a SQL query that modifies his payment amount in the travel system's database and passes it as one of the parameters . A backend batch payment system later fetches the payment amount from the database (the modified payment amount) and sends to the credit card processor, enabling the attacker to purchase the airfare at a lower price. An attacker needs to have some knowledge of the system's database, perhaps by exploiting another weakness that results in information disclosure.

+ Attacker Skills or Knowledge Required

Skill or Knowledge Level: Medium

If the attacker is able to gain good understanding of the system's database schema

Skill or Knowledge Level: High

If the attacker has to perform SQL injection blindly

+ Resources Required

None: No specialized resources are required to execute this type of attack.

+ Probing Techniques

Inject SQL characters in SOAP parameters and observe system behavior

Review WSDL to understand what is expected by the service provider

+ Solutions and Mitigations

Properly validate and sanitize/reject user input at the service provider.

Ensure that prepared statements or other mechanism that enables parameter binding is used when accessing the database in a way that would prevent the attackers' supplied data from controlling the structure of the executed query.

At the database level, ensure that the database user used by the application in a particular context has the minimum needed privileges to the database that are needed to perform the operation. When possible, run queries against pre-generated views rather than the tables directly.

+ Attack Motivation-Consequences
ScopeTechnical ImpactNote
Modify application data
Unexpected State
Read application data
Gain privileges / assume identity
Execute unauthorized code or commands
Run Arbitrary Code
+ Relevant Security Requirements

Always safely access the database through prepared statements that leverage parameter binding

Properly validate all SOAP parameters to ensure that their values are as expected

Reject bad user input (do not try to sanitize it)

+ Purposes
  • Exploitation
+ CIA Impact
Confidentiality Impact: HighIntegrity Impact: HighAvailability Impact: High
+ Technical Context
Architectural Paradigms
+ Content History
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
CAPEC Content TeamThe MITRE Corporation2017-08-04Updated Resources_RequiredInternal

More information is available — Please select a different filter.
Page Last Updated or Reviewed: August 04, 2017