full-disclosure - Oracle Advisory: Overwrite any file via desname in Oracle Reports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1C09DF36EB7A3F489633C919E7413501150D7A@mapibe09.exchange.xchg>
Date: Tue Jul 19 13:43:10 2005
From: ak at red-database-security.com (Kornbrust, Alexander)
Subject: Oracle Advisory: Overwrite any file via desname
	in Oracle Reports

Hello

3 months ago (15-april-2005) I informed the Oracle Security Team
(secalert_us@...cle.com) that I will publish bug details if the bugs are
not fixed with the next critical patch update (CPU July 2005). I know
that Oracle products are complex and a good patch quality need some
time. That's why I offered Oracle additional time if 3 months are not
sufficient for fixing the bugs. Oracle never asked for more time.

Oracle's behaviour not fixing critical security bugs for a long time
(over 650 days) is not acceptable for their customers. Oracle put their
customers in danger. At least one critical vulnerability can be abused
from any attacker via internet.

I decided to publish these vulnerabilities because it is possible to
mitigate the risk of these vulnerabilities by using the workarounds
provided in the advisories.

Kind Regards

 Alexander Kornbrust

 www.red-database-security.com

##################################################

Red-Database-Security GmbH  - Oracle Security Advisory

Overwrite any file via desname in Oracle Reports

 Name                Overwrite any file via desname in Oracle Reports
 Systems Affected    Oracle Reports 6.0, 6i, 9i, 10g
 Severity            High Risk 
 Category            File overwrite
 Vendor URL          http://www.oracle.com 
 Author              Alexander Kornbrust (ak at
red-database-security.com) 
 Date                19 July 2005 (V 1.00) 
 Advisory            AKSEC2003-005
 Inital bug report   706 days ago
 Advisory-URL
http://www.red-database-security.com/advisory/oracle_reports_overwrite_a
ny_file.html

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.

By specifing a special value for the parameter desname Oracle Reports
can
overwrite any file on the application server.
On Windows systems an attacker can overwrite any files (e.g. boot.ini)
on the application server. On UNIX system an attacker can overwrite all
files (e.g. opmn.xml) which belongs to the Oracle Application Server
user.

This attack can be done with a simple URL.

TestURL
#######
Will be provided if a patch is available.

Workaround
##########
Available at
http://www.red-database-security.com/advisory/oracle_reports_overwrite_a
ny_file.html

Affected systems
################
All versions of Oracle Reports are affected.
All applications using Oracle Reports (e.g. E-Business-Suite, ...)

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 believe you need a patch to
protect your Oracle Application Server you should contact Oracle.

History
#######
12-aug-2003 Oracle secalert was informed

26-sep-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

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

(c) 2005 by Red-Database-Security GmbH - last update 19-july-2005