|
SQL Injection in Oracle Enterprise Manager (TARGET Parameter)
January 29, 2009
Risk Level:
Medium
Affected versions:
Oracle Enterprise Manager 10g Grid Control 10.2.0.4 and previous patchsets
Remote exploitable:
Yes (Authentication is needed)
Credits:
This vulnerability was
discovered and
researched by Esteban Martínez Fayó of Application
Security Inc.
Details:
SQL Injection works by attempting to modify the parameters passed to an application to change the SQL statements that are passed to a database. SQL injection can be used to insert additional SQL statements to be executed.
The "TARGET" parameter used in web page /em/console/reports/admin of Oracle Enterprise Manager web application is vulnerable to SQL Injection attacks. It may be possible for a malicious user to execute a function with the elevated privileges of the SYSMAN database user in the repository database. This user has the DBA role granted.
Impact:
This vulnerability allow a Oracle Enterprise Manager user with VIEW (or more) privileges to execute a function call with the elevated privileges of the SYSMAN database user.
Vendor Status:
Vendor was contacted and
a patch was released.
Workaround:
There is no workaround for this issue.
Fix:
Apply Oracle Critical Patch Update January 2009 available at Oracle Metalink.
CVE:
CVE-2008-5447
Links:
http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpujan2009.html
Timeline:
Vendor Notification -
7/11/2008
Vendor Response -
7/14/2008
Fix - 1/13/2009
Public Disclosure -
1/29/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.
|
