Oracle Database Servers wrapped procedure buffer overflow
| oracle-wrapped-procedure-bo (18666) |  High Risk |
Description:
Oracle Database Servers could allow a remote attacker to execute code, caused by a attack based buffer overflow. PL/SQL procedures can have code wrapped or encrypted. A remote attacker can create a wrapped procedure containing a long token in the text to overflow a buffer and execute arbitrary code with privileges of the Oracle user.
Consequences:
Gain Access
Remedy:
Apply the appropriate patch for your system, available from the Oracle Security Alert #68. See References.
References:
- Oracle Security Alert #68: This security alert addresses security vulnerabilities in Oracle¿s server products..
- BID-10871: Oracle Multiple Unspecified Vulnerabilities
- CVE-2004-1371: Stack-based buffer overflow in Oracle 9i and 10g allows remote attackers to execute arbitrary code via a long token in the text of a wrapped procedure.
- US-CERT VU#316206: Oracle Database Server contains several vulnerabilities
Platforms Affected:
- Oracle Database Server 10.1.0.2
- Oracle Database Server 9.0.1
- Oracle Database Server 9.0.1.2
- Oracle Database Server 9.0.1.3
- Oracle Database Server 9.0.1.4
- Oracle Database Server 9.0.1.5
- Oracle Database Server 9.0.2
- Oracle Database Server 9.0.2.4
- Oracle Database Server 9.2
- Oracle Database Server 9.2.0
- Oracle Database Server 9.2.0.1
- Oracle Database Server 9.2.0.2
- Oracle Database Server 9.2.0.3
- Oracle Database Server 9.2.0.5
- Oracle Database Server 9.2.2
- Oracle Database Server 9.2.3
Reported:
Dec 23, 2004
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net