|
Oracle Database SQL Injection vulnerability in DBMS_CDC_PUBLISH.DROP_CHANGE_SOURCE
April 26, 2010
Risk Level:
Medium
Affected versions:
Oracle Database Server version 9iR2
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:
Oracle Database provides the DBMS_CDC_PUBLISH PL/SQL package owned by SYS that is part of the Change Data Capture component. This package has a SQL Injection vulnerability in DROP_CHANGE_SOURCE procedure. A malicious user can call the vulnerable procedure of this package with specially crafted parameters and execute SQL statements with the elevated privileges of the SYS user.
Impact:
To exploit this vulnerability EXECUTE permission on the SYS.DBMS_CDC_PUBLISH package is required. By default users granted the EXECUTE_CATALOG_ROLE role have this permission granted. 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_PUBLISH package.
Fix:
Apply Oracle Critical Patch Update April 2010 available at Oracle Metalink.
CVE:
CVE-2010-0870
Links:
http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpuapr2010.html
http://www.appsecinc.com/resources/alerts/oracle/2010-02.shtml
Timeline:
Vendor Notification - 9/24/2007
Vendor Response - 9/28/2007
Fix - 4/13/2010
Public Disclosure - 4/26/2010
Application Security, Inc's database security solutions have helped over 2000 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.
|
