|
Oracle Database SQL Injection vulnerability in LT.ROLLBACKWORKSPACE
May 4, 2009
Risk Level:
High
Affected versions:
Oracle Database Server version 10gR1
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 "LT" PL/SQL package that is part of the Oracle Workspace Manager component (DBMS_WM public synonym). This package has a SQL Injection instance in ROLLBACKWORKSPACE procedure. Dependening on what Oracle Workspace Manager release is installed, this PL/SQL package is owned by SYS (on older releses) or by WMSYS (on newer releases). 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 package owner, depending on the system configuration it can be SYS or WMSYS.
Impact:
By default [WM]SYS.LT has EXECUTE permission to PUBLIC so any Oracle Database user can exploit this vulnerability. Exploitation of this vulnerability allows an attacker to execute SQL commands with SYS or WMSYS privileges.
Vendor Status:
Vendor was contacted and
a patch was released.
Workaround:
Restrict access to the [WM]SYS.LT package.
Fix:
Apply Oracle Critical Patch Update April 2009 available at Oracle Metalink.
CVE:
CVE-2009-0978
Links:
Application Security, Inc advisory: http://www.appsecinc.com/resources/alerts/oracle/2009-03.shtml
http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpuapr2009.html
Timeline:
Vendor Notification -
8/22/2007
Fix - 4/14/2009
Public Disclosure -
5/04/2009
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.
|
