SkipNavigation
US-CERT
American Flag
  Vulnerability
Notes
Database

Search Vulnerability Notes

Vulnerability Notes Help Information


 
 View Notes By
  Name

ID Number

CVE Name

Date Public

Date Published

Date Updated

Severity Metric



 Other Documents
  Technical Alerts

Technical Bulletins

Alerts

Security Tips

 

Vulnerability Note VU#805737

Oracle views fail to enforce table security settings

Overview

A vulnerability in the way Oracle handles views may allow an attacker to modify privileged database information.

I. Description

Database Views

A view is a queryable aggregation of data from one or more tables that is stored and maintained.

The Problem

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.

II. Impact

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.

III. Solution

Apply Updates

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.

Systems Affected

VendorStatusDate NotifiedDate Updated
Oracle CorporationVulnerable3-May-2006

References


http://www.red-database-security.com/advisory/oracle_modify_data_via_views.html
http://www.oracle.com/technology/deploy/security/pdf/twp_security_checklist_db_database.pdf
http://www.oracle.com/technology/deploy/security/db_security/htdocs/eus.html
http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpujul2006.html
http://andrewmax.blogspot.com/2006/04/yet-another-security-alert.html

Credit

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.

Other Information

Date Public:2006-04-06
Date First Published:2006-05-03
Date Last Updated:2007-01-03
CERT Advisory: 
CVE-ID(s): 
NVD-ID(s): 
US-CERT Technical Alerts: 
Metric:12.66
Document Revision:107

If you have feedback, comments, or additional information about this vulnerability, please send us email.
 

 
Page Corner Image
Produced 2006 by US-CERT, a government organization
Disclaimers and copyright information
Get Adobe Reader Get Adobe Reader