Watch your door-attack server (3)-soap injection attack

The first thing to declare is that this article is purely an ignorant view of a little developer without foresight and knowledge, and is intended only for reference in Web system security.

1. Soap Injection attack

The server-side XML parsing engine receives input from the client, which can refer to a browser, data from a Web application, a mobile device, or other type of source. If the input information is not properly verified, the result of the received is likely to be wrong, thus facilitating the attack behavior.
From a practical point of view, the injection attack vulnerability to soap is very difficult to find, because the data is often transmitted through the interface, and many of the interfaces to the error is processed.

2. The principle of SOAP injection attack

The main body of soap communication is that Xml,xml has a lot of characteristics and characteristics, if the character stream is caught or deliberately attacked, the response of the service side changes;
If you do not do some filtering, some very important properties will be lent out;

3. A typical case of soap injection attacks

Related manufacturers: it168.com
Discovery Time: November 2013
Detailed Description:
SOAP injection:

http://webservicen.it168.com/service.asmx?wsdl

Presence Injection Parameter ProductID

Code codes

<soap-env:header/>     <soap-env:body>        <urn:multiproductidtofindarticle>           <urn:productid>Injection point '</urn:productid>           <Urn:articletypeid>1</Urn:articletypeid>           <urn:pagesize>20</urn:pagesize>           <urn:sttime>1</urn:sttime>           <urn:endtime>1</urn:endtime>           <urn:regionalid>NY</urn:regionalid>           <urn:pagenumber>20</urn:pagenumber>        </urn:multiproductidtofindarticle>     </soap-env:body></soap-env:envelope>Vulnerability Proof: Database version, etc.

Watch your door-attack server (3)-soap injection attack