Read parts of any XML-file via customize parameter in Oracle Reports

Type securityvulns
Reporter Securityvulns
Modified 2005-07-19T00:00:00


Name Read parts of any XML-file via customize parameter in Oracle Reports Systems Affected All version of Oracle Reports Severity Medium Risk Category Information disclosure Vendor URL Author Alexander Kornbrust (ak at Date 19 July 2005 (V 1.00) Advisory AKSEC2003-007 Inital bug report 693 days ago

Details Oracle Reports is Oracle's award-winning, high-fidelity enterprise reporting tool. It enables businesses to give immediate access to information to all levels within and outside of the organization in an unrivaled scalable and secure environment. Oracle Reports, a component of the Oracle Application Server, is used by Oracle itself for the E-Business Suite. Many large customers are using Oracle Reports as reporting tool for their enterprise applications.

The Oracle Reports parameter customize can read any file by using an absolute or relative file name. Parts of the file content are displayed in the Reports error message (see test case).



Reports Output*

REP--866648059: Error in the XML report definition at line 3 in ' Element 'CALYPSO' used but not declared.'.

Reports Output*

Workaround for Oracle Reports Use URLRewrite to block potential dangerous URLs with customize parameter. RewriteLog /anywhere/rewrite.log RewriteEngine On RewriteRule (.)customize(.)$ /forbidden.htm[R] [NC]

If you need the customize parameter in your URL you can create a new entry in the cgicmd.dat (e.g. mycust: customize=/myfiles/myfile.xml).

Don't forget to protect the content of your cgicmd.dat by setting the environment variable REPORTS_CGINODIAG=YES (see Metalink article 274858.1).

Affected systems All versions of Oracle Reports are affected.

Patch Information This bug is NOT FIXED with Critical Patch Update July 2005 (CPU July 2005). It seems that Oracle is NOT INTERESTED to fix this issue and provide patches for this issue. If you think you need a patch to protect your Oracle Application Server you should contact Oracle.

History 26-aug-2003 Oracle secalert was informed

27-aug-2003 Bug confirmed

15-apr-2005 Red-Database-Security informed Oracle secalert that this vulnerability will publish after CPU July 2005 Red-Database-Security offered Oracle more time if it is not possible to provide a fix ==> NO FEEDBACK.

12-jul-2005 Oracle published CPU July 2005 without fixing this issue

18-jul-2005 Red-Database-Security published this advisory

© 2005 by Red-Database-Security GmbH - last update 19-july-2005