Vulnerability Note VU#736923
Oracle 9iAS SOAP components allow anonymous users to deploy applications by default
Oracle Application Server 9iAS installs with Simple Object Access Protocol (SOAP) enabled by default and allows unauthenticated remote users to deploy and undeploy SOAP services and providers.
Oracle Application Server 9iAS supports Simple Object Access Protocol (SOAP), an XML-based protocol used by Oracle for Web administration of database services. Version 126.96.36.199.1 of Oracle 9iAS installs with SOAP components enabled by default. The typical installation of this Oracle product also includes SOAP tools that allow remote Web users to deploy and undeploy SOAP services and providers on the server, without authentication and without notice to the Oracle system adminstrator.
An attacker can control aspects of the Oracle system in ways not intended by its administrators. The attacker may be able to obtain or modify data or perform other actions that are not authorized.
The CERT/CC is currently unaware of a practical solution to this problem.
The following workarounds were suggested by David Litchfield and have not been tested by CERT/CC.
To disable SOAP, delete or comment-out the following lines in the file named "$ORACLE_HOME/Apache/Jserv/etc/jserv.conf":
ApJServGroup group2 1 1
ApJServMount /soap/servlet ajpv12://localhost:8200/soap
ApJServMount /dms2 ajpv12://localhost:8200/soap
ApJServGroupMount /soap/servlet balance://group2/soap
Note that in the lines above, "$ORACLE_HOME" may be spelled out, and the port number may differ from 8200.
To prevent SOAP services from being deployed or undeployed, add the following line to the file named "$ORACLE_HOME/soap/werbapps/soap/WEB-INF/config/soapConfig.xml":
<osc:option name="autoDeploy" value="false" />
If you are a vendor and your product is affected, let
|Vendor||Status||Date Notified||Date Updated|
|Oracle||Affected||08 Feb 2002||26 Feb 2002|
Thanks to David Litchfield for reporting this vulnerability.
This document was written by Shawn Van Ittersum.
10 Jan 2002
Date First Published:
12 Mar 2002
Date Last Updated:
12 Mar 2002
If you have feedback, comments, or additional information about this vulnerability, please send us email.