Oracle Updates for Multiple Vulnerabilities

Original release date: January 12, 2010
Last revised: --
Source: US-CERT

Systems Affected

• Oracle Database 11g, version 11.1.0.7
• Oracle Database 10g Release 2, versions 10.2.0.3, 10.2.0.4
• Oracle Database 10g, version 10.1.0.5
• Oracle Database 9i Release 2, versions 9.2.0.8, 9.2.0.8DV
• Oracle Application Server 10g Release 3 (10.1.3), versions 10.1.3.4.0, 10.1.3.5, 10.1.3.5.1
• Oracle Application Server 10g Release 2 (10.1.2), version 10.1.2.3.0
• Oracle Access Manager versions 7.0.4.3, 10.1.4.2
• Oracle E-Business Suite Release 12, versions 12.0.4, 12.0.5, 12.0.6, 12.1.1 and 12.1.2
• Oracle E-Business Suite Release 11i, version 11.5.10.2
• PeopleSoft Enterprise HCM (TAM), versions 8.9 and 9.0
• Oracle WebLogic Server 10.0 through MP2, 10.3.0 and 10.3.1
• Oracle WebLogic Server 9.0 GA, 9.1 GA and 9.2 through 9.2 MP3
• Oracle WebLogic Server 8.1 through 8.1 SP6
• Oracle WebLogic Server 7.0 through 7.0 SP7
• Oracle JRockit R27.6.5 and earlier (JDK/JRE 6, 5, 1.4.2)
• Primavera P6 Enterprise Project Portfolio Management 6.1, 6.2.1 and 7.0
• Primavera P6 Web Services 6.2.1, 7.0 and 7.0SP1

Overview

Oracle products and components are affected by multiple vulnerabilities. The impacts of these vulnerabilities include remote execution of arbitrary code, information disclosure, and denial of service.

I. Description

The Oracle Critical Patch Update Advisory - January 2010 addresses 24 vulnerabilities in various Oracle products and components. The document provides information about affected components, access and authorization required for successful exploitation, and the impact from the vulnerabilities on data confidentiality, integrity, and availability.

Oracle has associated CVE identifiers with the vulnerabilities addressed in this Critical Patch Update. If significant additional details about vulnerabilities and remediation techniques become available, we will update the Vulnerability Notes Database.

II. Impact

The impact of these vulnerabilities varies depending on the product, component, and configuration of the system. Potential consequences include the execution of arbitrary code or commands, information disclosure, and denial of service. Vulnerable components may be available to unauthenticated, remote attackers. An attacker who compromises an Oracle database may be able to access sensitive information.

III. Solution

Apply the appropriate patches or upgrade as specified in the Oracle Critical Patch Update Advisory - January 2010. Note that this document only lists newly corrected issues. Updates to patches for previously known issues are not listed.

IV. References

• Oracle Patch Update Advisory - January 2010 - <http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpujan2010.html>
• Critical Patch Updates and Security Alerts - <http://www.oracle.com/technology/deploy/security/alerts.htm>
• Map of Public Vulnerability to Advisory/Alert - <http://www.oracle.com/technology/deploy/security/critical-patch-updates/public_vuln_to_advisory_mapping.html>