Application Security, Inc.
home client login partner login online store contact us
search:
Solutions Products Partners Support News & Events About Us

Team SHATTER Security Advisory

Oracle Database SQL Injection in SYS.DBMS_CDC_UTILITY.LOCK_CHANGE_SET (DB02)

April 28, 2008

Risk Level:
Medium

Affected versions:
Oracle Database Server versions 9iR1, 9iR2, 10gR1, 10gR2 and 11gR1

Remote exploitable:
Yes (Authentication to Database Server is needed)

Credits:
This vulnerability was discovered and researched by Esteban Martínez Fayó of Application Security Inc.

Details:
The PL/SQL package DBMS_CDC_UTILITY owned by SYS has an instance of SQL Injection. A malicious user can call a vulnerable procedure of this package with specially crafted parameters and execute SQL statements with the elevated privileges of the SYS user.

Impact:
Any Oracle database user with EXECUTE privilege on the package SYS.DBMS_CDC_UTILITY can exploit this vulnerability. By default, users granted SELECT_CATALOG_ROLE have the required privilege. Exploitation of this vulnerability allows an attacker to execute SQL commands with SYS privileges.

Vendor Status:
Vendor was contacted and a patch was released.

Workaround:
Restrict access to the SYS.DBMS_CDC_UTILITY package.

Fix:
Apply Oracle Critical Patch Update April 2008 available at Oracle Metalink.

Links:
http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpuapr2008.html

Timeline:
Vendor Notification - 9/24/2007
Vendor Response - 9/28/2007
Fix - 4/15/2008
Public Disclosure - 4/28/2008

Application Security, Inc's database security solutions have helped over 1000 organizations secure their databases from all internal and external threats while also ensuring that those organizations meet or exceed regulatory compliance and audit requirements.

Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.