July 31, 2003
In a paper titled "Variations in exploit methods between Linux and Windows" presented at Blackhat 2003, David Litchfield has illustrated multiple vulnerabilities in the Oracle 9i XML Database (XDB).
Successful exploits may allow remote attackers to run arbitrary code in the security context of the vulnerable service.
- Oracle Oracle9i Enterprise Edition 9.2.0 .0.1
- Oracle Oracle9i Personal Edition 9.2.0 .0.1
- Oracle Oracle9i Standard Edition 9.2.0 .0.1
Block external access at the network boundary, unless external parties require service.
If applicable, filter traffic at the network perimeter. Allow traffic destined for the affected server from trusted hosts and networks only. Deny all other communications. Filter traffic to ports 8080 and 2100.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
NIDS will help detect malicious traffic, build effective firewall rules, and prevent further attacks on vulnerable applications.
Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.
Disable any services that are not needed.
This vulnerability is remotely exploitable through services enabled by default. Disabling such services may close future channels of attack.
Oracle has released patches to address these issues. See the referenced advisory (Oracle Security Alert 58) for details on obtaining and applying patches using the Oracle metalink site tool.
Discovery of these vulnerabilities has been credited to David Litchfield(email@example.com).
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com
are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.