Multiple vulnerabilities have been reported for various Oracle products. Some of these have unknown impacts, while others can be exploited to disclose potentially sensitive information, bypass certain security restrictions and conduct cross-site scripting and SQL injection attacks, cause a DoS (Denial of Service), and potentially compromise a vulnerable system.

Details are available for the following vulnerabilities:

1) Oracle APEX does not correctly sanitise input passed via the password used in the wwv_flow_security.check_db_password function before using it in SQL queries. This can be exploited to modify SQL queries by injecting arbitrary SQL code.

2) Specially crafted views can be exploited to perform updates, deletes and inserts without having proper privileges.

3) Certain input processed by the DBMS_PRVTAQIS package is not correctly sanitised before being used in SQL queries. This can be exploited to modify SQL queries by injecting arbitrary SQL code.

4) Errors within various public procedures exist in the MDSYS.MD package. These can be exploited to cause buffer overflows, resulting in a DoS or potentially the execution of arbitrary code.

5) An error exists within the "GET_PROPERTY" function in the SYS.DBMS_DRS package. This can be exploited to cause a buffer overflow, resulting in a DoS or potentially the execution of arbitrary code.

6) Certain unspecified input passed to the Oracle Configurator of the Oracle E-Business Suite is not properly sanitised before being returned to a user. This can be exploited to execute HTML and script code in a user's browser session in context of a vulnerable site.

7) Certain unspecified input passed to the Oracle Internet Expenses web page of the Oracle E-Business Suite is not properly sanitised before being returned to a user. This can be exploited to execute HTML and script code in a user's browser session in context of a vulnerable site.

Note: By default, this page is blocked by the URL firewall.

8) Certain unspecified input passed to the Oracle On-line help of the Oracle E-Business Suite is not properly sanitised before being returned to a user or used in SQL queries. This can be exploited to execute HTML and script code in a user's browser session in context of a vulnerable site or to manipulate SQL queries by injecting arbitrary SQL code.

9) Certain unspecified input passed to the Costumer Intelligence is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

10) An unspecified error within iPayments can be exploited to disclose potentially sensitive information via unknown vectors.

11) Certain unspecified input passed to the Application Object Library is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

12) Certain unspecified input passed to the Human Resources is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

Successful exploitation of vulnerabilities #6, #7, #9, #10, and #12 requires a valid session.

Note: The password storage in iRecruitment and the storage of taxpayer identification numbers in Payables was enhanced.

Solution
Apply patches (See vendor's advisory).

Provided and/or discovered by
The vendor credits:
* Esteban Martinez Fayo of Application Security, Inc.
* Jack Kanter and Stephen Kost of Integrigy
* Guy Karlebach of Imperva
* Joxean Koret
* Alexander Kornbrust of Red Database Security GmbH
* Michael Krax
* David Litchfield and Paul M. Wright of Next Generation Security Software Ltd.

Changelog
Further details available in Customer Area

Original Advisory
Oracle:
http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpujul2007.html

Red Database Security:
http://www.red-database-security.com/advisory/oracle_apex_sql_injection_check_db_password.html
http://www.red-database-security.com/advisory/oracle_view_vulnerability.html
http://www.red-database-security.com/advisory/oracle_sql_injection_dbms_prvtaqis.html

Application Security Inc.:
http://www.appsecinc.com/resources/alerts/oracle/2007-04.shtml
http://www.appsecinc.com/resources/alerts/oracle/2007-05.shtml

Integrigy:
http://www.integrigy.com/security-resources/analysis/Integrigy_Oracle_CPU_July_2007_Analysis.pdf

Other references
Further details available in Customer Area

Deep Links
Links available in Customer Area