A vulnerability in the way Oracle handles views may allow an attacker to modify privileged database information.
A view is a queryable aggregation of data from one or more tables that is stored and maintained.
A vulnerability in the way that Oracle handles specially crafted views may allow an attacker to bypass Oracle security settings and modify the underlying tables on which the view is built.
Originally, it was believed that an attacker must have the
CREATE VIEW privilege and
SELECT privileges on certain tables to exploit this vulnerability. However, according to public sources, the
CREATE VIEW privilege is not needed.
Note that exploit code for this issue is publicly available.
A remote attacker may be able to execute arbitrary SQL statements with elevated privileges. This may allow the attacker to access and modify sensitive information within an Oracle database.
We believe this issue is addressed in the Oracle Critical Patch Update for January 2006.
Until the update for this issue can be applied, the following workarounds may reduce the chances of exploitation.
Use Least Privilege
Where possible, grant users the fewest privileges needed to perform necessary tasks. Adding or removing privileges from roles may impact system functionality. Instead, privileges should be administered on a per-user basis.
Change login credentials for default Oracle accounts
Oracle creates numerous default accounts when it is installed. Upon installation, accounts that are not needed should be disabled and the login credentials for needed accounts should be changed.
Vendor| Status| Date Notified| Date Updated
Oracle Corporation| | 12 Apr 2006| 03 May 2006
If you are a vendor and your product is affected, let us know.
Group | Score | Vector
Base | N/A | N/A
Temporal | N/A | N/A
Environmental | N/A | N/A
This vulnerability was reported by Alexander Kornbrust of Red Database Security . Red Database Security credits Jens Flasche, Dr. Christian Kleinewächter, and Swen Thümmler with providing information regarding this issue. Information used in this document came from Oracle .
This document was written by Jeff Gennari and Stephen Rhoton .