Home > CAPEC List > CAPEC-256: SOAP Array Overflow (Version 2.9)  

CAPEC-256: SOAP Array Overflow

SOAP Array Overflow
Definition in a New Window Definition in a New Window
Attack Pattern ID: 256
Abstraction: Detailed
Status: Draft
Completeness: Stub
Presentation Filter:
+ Summary

An attacker sends a SOAP request with an array whose actual length exceeds the length indicated in the request. When a data structure including a SOAP array is instantiated, the sender transmits the size of the array as an explicit parameter along with the data. If the server processing the transmission naively trusts the specified size, then an attacker can intentionally understate the size of the array, possibly resulting in a buffer overflow if the server attempts to read the entire data set into the memory it allocated for a smaller array. This, in turn, can lead to a server crash or even the execution of arbitrary code.

+ Attack Prerequisites
  • The targeted SOAP server must trust that the array size as stated in messages it receives is correct, but read through the entire content of the message regardless of the stated size of the array.

+ Typical Severity


+ Resources Required

The attacker must be able to craft malformed SOAP messages, specifically, messages with arrays where the stated array size understates the actual size of the array in the message.

+ Solutions and Mitigations

If the server either verifies the correctness of the stated array size or if the server stops processing an array once the stated number of elements have been read, regardless of the actual array size, then this attack will fail. The former detects the malformed SOAP message while the latter ensures that the server does not attempt to load more data than was allocated for.

+ References
[R.256.1] Robin Cover, ed.. "XML and Web Services In The News". XML Daily Newslink. <http://www.xml.org/xml/news/archives/archive.11292006.shtml>.
[R.256.2] "Simple Object Access Protocol (SOAP) 1.1". 5.4.2 Arrays. W3C. November 29, 2006. <http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383522>.
+ Content History
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team

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