Oracle 9iAS default configuration allows arbitrary users to view sensitive configuration files

Overview

It is possible to read the “XSQLConfig.xml” and “soapConfig.xml” configuration files from an Oracle 9i Application Server under the default installation without any authorization. This can lead to an intruder gaining access to sensitive information about the server and potentially compromising it.

Description

The XSQL configuration and SOAP configuration files contain sensitive information such as the database server host name, user ID’s and passwords. Since these files are not protected by default, any user can access it directly through a virtual directory and view the contents.

---

Impact

An intruder can gain sensitive information about the configuration of the server. This information can be used to compromise the server.

---

Solution

Apply the appropriate permissions to these files, please see Oracle’s Security Alert on this issue.

---

Apply the appropriate permissions to the “XSQLConfig.xml” and “soapConfig.xml” configuration files.

---

Vendor Information

476619

Filter by status: All Affected Not Affected Unknown

Filter by content: __ Additional information available

__ Sort by: Status Alphabetical

Expand all

Javascript is disabled. Click here to view vendors.

Oracle __ Affected

Notified: February 13, 2002 Updated: February 27, 2002

Status

Affected

Vendor Statement

Please see Oracle’s Security Alert at <http://otn.oracle.com/deploy/security/pdf/ojvm_alert.pdf&gt;.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23476619 Feedback>).

CVSS Metrics

Group	Score	Vector
Base
Temporal
Environmental

References

<http://www.nextgenss.com/papers/hpoas.pdf&gt;

Acknowledgements

Our thanks to David Litchfield of NGSSoftware, who reported on this vulnerability.

This document was written by Jason Rafail and is based on the report by David Litchfield.

Other Information

CVE IDs:	CVE-2002-0568
Severity Metric:	42.19 Date Public: