First published: Sat Jan 25 2014(Updated: )
The WSDL/WADL import functionality in SoapUI before 4.6.4 allows remote attackers to execute arbitrary Java code via a crafted request parameter in a WSDL file.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/com.smartbear.soapui:soapui | <4.6.4 | 4.6.4 |
SoapUI | =2.5.1 | |
SoapUI | =3.0.1 | |
SoapUI | =3.5 | |
SoapUI | =3.5.1 | |
SoapUI | =3.6 | |
SoapUI | =3.6.1 | |
SoapUI | <=4.6.3 | |
SoapUI | =4.0 | |
SoapUI | =4.0-beta1 | |
SoapUI | =4.0-beta2 | |
SoapUI | =4.0.1 | |
SoapUI | =4.5 | |
SoapUI | =4.5.1 | |
SoapUI | =4.5.2 | |
SoapUI | =4.6.0 | |
SoapUI | =4.6.1 | |
SoapUI | =4.6.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-1202 is classified as a critical vulnerability due to its potential for remote code execution.
To fix CVE-2014-1202, upgrade to SoapUI version 4.6.4 or later.
CVE-2014-1202 affects multiple versions of SoapUI, specifically versions prior to 4.6.4, including 2.5.1, 3.0.1, 3.5, and others.
The risks associated with CVE-2014-1202 include the potential for unauthorized remote code execution, allowing attackers to execute arbitrary Java code.
There is no official workaround for CVE-2014-1202; the recommended solution is to upgrade to the latest version.