Oracle Critical Patch Update - January 2007

Description

A Critical Patch Update is a collection of patches for multiple security vulnerabilities. It also includes non-security fixes that are required (because of interdependencies) by those security patches. This Critical Patch Update contains 51 new security fixes across all products.

Supported Products and Components Affected

Security vulnerabilities addressed by this Critical Patch Update affect the products listed in the categories below. The product area of the patches for the listed versions is shown in [square brackets] following the product versions. Please click on the link in [square brackets] or in the Patch Availability Table to access the documentation for those patches.

Product releases and versions that are in Premier Support or Extended Support, under the Oracle Lifetime Support policy; or Error Correction Support (ECS) or Extended Maintenance Support (EMS), under the previous support policy:

Products and components that are bundled with the products listed in Category I:

Products that are de-supported as a standalone installation but are supported when installed with the products listed in Category I:

Patches for Category III products are only available when these products are installed as part of Category I products, and are tested solely on supported configurations and environments. Please refer to the documentation for each product for specific details concerning the support and availability of patches.

Products that are supported only on selected platforms. Please consult the additional documentation for details.

Patch Availability Table and Risk Matrices

The Oracle Database, Oracle Application Server, Oracle Enterprise Manager Grid Control, Oracle Collaboration Suite, JD Edwards EnterpriseOne, JD Edwards OneWorld Tools, PeopleSoft Enterprise Portal Applications and PeopleSoft Enterprise PeopleTools patches in the Updates are cumulative; each Critical Patch Update contains the fixes from the previous Critical Patch Updates.

Oracle E-Business Suite and Applications patches are not cumulative, so E-Business Suite and Applications customers should refer to previous Critical Patch Updates to identify previous fixes they want to apply.

For each Oracle product being administered, please consult the documentation for patch availability information and installation instructions referenced from the following table. For an overview of the Oracle product documentation related to this Critical Patch Update, please refer to the Oracle Critical Patch Update January 2007 Documentation Map, MetaLink Note 405814.1.

Risk Matrix Content

Risk matrices list only security vulnerabilities that are newly fixed by the patches associated with this advisory. Risk matrices for previous fixes can be found in previous Critical Patch Update advisories.

Several vulnerabilities addressed in this Critical Patch Update affect multiple products. The same vulnerability appears with the same Vuln # in all risk matrices. Italics indicate vulnerabilities in code included from other product areas.

Oracle conducts an analysis of each security vulnerability addressed by a Critical Patch Update (CPU) or a Security Alert. Results of the security analysis are reflected in the associated documentation describing, for example, the type of vulnerability, the conditions required to exploit it and the result of a successful exploit. Oracle provides this information, in part, so that customers may conduct their own risk analysis based on the particulars of their product usage. As a matter of policy, Oracle does not disclose detailed information about an exploit condition or results that can be used to conduct a successful exploit. Oracle will not provide additional information about the specifics of vulnerabilities beyond what is provided in the CPU or Security Alert notification, the Patch Availability Matrix, the readme files, and FAQs. Oracle does not provide advance notification on CPU or Security Alerts to individual customers. Finally, Oracle does not distribute exploit code nor “proof-of-concept” code for vulnerabilities in our products.

Workarounds

Due to the threat posed by a successful attack, Oracle strongly recommends that fixes are applied as soon as possible. Depending on your environment, it may be possible to reduce the risk of successful attack by restricting network protocols required by an attack. For attacks that require certain privileges or access to certain packages, removing the privileges or the ability to access the packages from untrusted users may help reduce the risk of successful attack. Both approaches may break application functionality, so Oracle strongly recommends changes are tested on non-production systems. Neither approach should be considered a long term solution as neither corrects the underlying problem.

Unsupported Products and De-Supported Versions

Unsupported products, releases and versions are not tested for the presence of vulnerabilities addressed by this Critical Patch Update. However, it is likely that earlier patch sets of affected releases are also affected by these vulnerabilities.

Supported products are patched in accordance with the Critical Patch Update policy summarized in the CPU Frequently Asked Questions document linked from the References section.

Critical Patch Update patches are available for customers who have purchased Extended Maintenance Support (EMS) before the implementation of the Lifetime Support Policy. De-support Notices indicate whether EMS is available for a particular release and platform, as well as the specific period during which EMS will be available.

Customers with valid licenses for product versions covered by Extended Support (ES), before the implementation of the Lifetime Support Policy, are entitled to download existing fixes; but new issues that may arise from the application of patches are not covered under ES. Therefore, ES customers should have comprehensive plans to enable removal of any applied patch.

Critical Patch Update patches are not provided for product versions which are no longer covered under the Extended Maintenance Support plan or the Lifetime Support Policy. We recommend that customers upgrade to the latest supported version of Oracle products in order to obtain patches.

Please review the "Extended Support" section within the Technical Support Policies for further guidelines regarding ES and EMS.

Credits

The following people discovered and brought security vulnerabilities addressed by this Critical Patch Update to Oracle's attention: Andy Davis of Information Risk Management Plc; Vicente Aguilera Diaz of Internet Security Auditors, S.L.; Esteban Martinez Fayo of Application Security, Inc.; Tony Fogarty of BT Global Services; Oliver Karow of Symantec; Joxean Koret; Alexander Kornbrust of Red Database Security GmbH; David Litchfield and Mark Litchfield of Next Generation Security Software Ltd.; and noderat ratty.

Critical Patch Update Schedule

Critical Patch Updates are released on the Tuesday closest to the 15th day of January, April, July and October. The next four dates are:

• 17 April 2007
• 17 July 2007
• 16 October 2007
• 15 January 2008

• Oracle Critical Patch Updates and Security Alerts main page  [ Oracle Technology Network ]
• Oracle PeopleSoft Security main page  [ Customer Connection ]
• Critical Patch Update - January 2007 Documentation Map   [ MetaLink Note 405814.1 ]
• Oracle Critical Patch Updates and Security Alerts - Frequently Asked Questions [ MetaLink Note 360470.1 ]
• Common Vulnerability Scoring System (CVSS) Risk Matrix definitions   [ MetaLink Note 394486.1 ]   [ Customer Connection ]
• Use of Common Vulnerability Scoring System (CVSS) by Oracle   [ MetaLink Note 394487.1 ]   [ Customer Connection ]
• List of public vulnerabilities fixed in Critical Patch Updates and Security Alerts   [ Oracle Technology Network ]

Modification History

Oracle Database Executive Summary

This Critical Patch Update contains a total of 26 new security fixes for Oracle Database products, divided as follows:

• 17 new security fixes for the Oracle Database, 1 of which may be remotely exploitable without authentication, i.e. it may be exploited over a network without the need for a username and password. 1 fix is applicable to Oracle Database client-only installations, i.e. installations that do not have the Oracle Database installed.
• 9 new security fixes for Oracle HTTP Server, 8 of which may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. Oracle HTTP Server is an optional product that is not installed by default with the Oracle Database. If it has not been installed, this software will not be present and the Oracle HTTP Server patches are not required. Oracle Database versions up to and including Oracle Database 9i Release 2 allowed Oracle HTTP Server to be installed as an optional component of the database. Oracle Database versions 10g Release 1 and higher include Oracle HTTP Server on the Companion CD.
• There are no new security fixes for Oracle Application Express (formerly called HTML DB), but versions up to and including version 2.0 should be upgraded to the latest version. Oracle Application Express is an optional product that is not installed with the Oracle Database. If it has not been installed (it is provided on the Companion CD in the Oracle Database CD set for some Oracle Database versions), this software will not be present and the patches are not required.
  Please refer to Appendix A in the October 2006 Critical Patch Update advisory for more information.

Notes:

• Vulnerabilities with a CVSS base score of 0.0 represent problems that are not exploitable in a default database environment. If custom code runs affected programs as a privileged user, it may allow malicious code to be run as that user.

Oracle Database Client-only Installations

One new database vulnerability addressed by this Critical Patch Update, DB11, affects Oracle Database client-only installations (installations that do not have the Oracle Database installed). It is potentially exploitable where a privileged operating system process is passing input from an untrusted source to the affected program. Oracle recommends applying this Critical Patch Update to client-only installations which may be using the affected program in this way, or which are affected by client-only issues fixed in prior Critical Patch Updates if the prior patches have not been applied.

Client-side software in the middle tier is patched as part of the general middle tier patch and customers do not need to apply additional patches. Exceptions will be documented in the Patch Availability Document for Oracle Server and Middleware Products, or the Pre-Installation Note, depending on the product.

Oracle Application Server Executive Summary

This Critical Patch Update contains 12 new security fixes for Oracle Application Server, 8 of which may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. No new fixes are applicable to client-only installations, i.e. installations that do not have Oracle Application Server installed.

This Critical Patch Update also contains 8 new security fixes for Oracle Application Server products that are not supported for standalone use, but are supported for use as part of supported products, i.e. those listed in the Category I section. More details of these fixes can be found in the sections of this document covering: Oracle Database, Oracle Collaboration Suite and Oracle E-Business Suite. They are not discussed further in this section, as they do not apply to Oracle Application Server standalone instances.

Oracle Application Server products that are bundled with the Oracle Database are affected by the vulnerabilities listed in the Oracle Database section. They are not discussed further in this section and are not listed in the Oracle Application Server risk matrix.

Notes:

• OC4J03 requires manual steps to be performed. Details can be found in the Patch Availability Document for Oracle Server and Middleware Products, MetaLink Note 403325.1.

Oracle Application Server Client-only Installations

No new vulnerabilities addressed by this Critical Patch Update affect client-only installations of Application Server products. However, fixes for Oracle Containers for J2EE and Oracle Reports Developer which affect client-only installations were released in the October 2006 Critical Patch Update. Please refer to the October 2006 Critical Patch Update advisory for more information if these patches have not yet been applied.

Oracle Collaboration Suite Executive Summary

There are no new Oracle Collaboration Suite specific fixes in this Critical Patch Update. Please refer to the July 2006 Critical Patch Update for the latest Oracle Collaboration Suite specific fixes.

This Critical Patch Update contains 14 Oracle Application Server vulnerabilities that are in code included in Oracle Collaboration Suite. 11 of these vulnerabilities may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. The application tier stack patch supplied as part of this Critical Patch Update contains these fixes and should be installed on Oracle Collaboration Suite instances.

Oracle Collaboration Suite bundles the Oracle Database. All the fixes listed in the Oracle Database part of the Oracle Database section are applicable. The Oracle Collaboration Suite documentation referenced from this advisory lists the patches that should be installed on Oracle Collaboration Suite instances to fix these Oracle Database issues.

Oracle E-Business Suite and Applications Executive Summary

This Critical Patch Update contains 7 new security fixes for the Oracle E-Business Suite, including one in Oracle Workflow Cartridge. None of these vulnerabilities may be remotely exploited without authentication.

Oracle E-Business Suite includes Oracle9i Application Server Release 1, version 1.0.2.2 code, including Oracle Reports Developer. 6 Oracle Application Server vulnerabilities are applicable to this version of the code, and all may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. The application tier stack patch supplied as part of this Critical Patch Update contains these fixes and should be installed on Oracle E-Business Suite instances.

Oracle E-Business Suite products include an Oracle Database which is affected by the vulnerabilities listed in the Oracle Database section. The exposure of Oracle E-Business Suite products is dependent on the Oracle Database version being used. Oracle Database vulnerabilities are not listed in the Oracle E-Business Suite risk matrix, but should be patched.

There are no new security fixes specific to Oracle Life Sciences Applications (previously known as Oracle Pharmaceutical Applications).

Oracle Life Sciences Applications includes Oracle Application Server components which should be patched. The exposure of Oracle Life Sciences Applications depends on the version of Oracle Application Server being used. The E-Business Suite risk matrix includes Oracle Application Server vulnerabilities applicable to Oracle9i Application Server Release 1, version 1.0.2.2, and the Oracle Application Server section lists vulnerabilities applicable to other versions.

Oracle Life Sciences Applications includes Oracle Database software which is affected by the vulnerabilities listed in the Oracle Database section. The exposure of Oracle Life Sciences Applications is dependent on the Oracle Database version being used. Oracle Database vulnerabilities are not listed in the Oracle Life Sciences Applications risk matrix, but should be patched.

Oracle Life Sciences Applications customers should refer to MetaLink Note 403803.1 for detailed information on installing Oracle Application Server and Oracle Database security patches.

Oracle Enterprise Manager Executive Summary

This Critical Patch Update contains 6 new security fixes for Oracle Enterprise Manager, 5 of which may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password.

Oracle Enterprise Manager includes Oracle Database and Oracle Application Server components which are affected by the vulnerabilities listed in the Oracle Database and Oracle Application Server sections. The Oracle Database and Oracle Application Server vulnerabilities that affect a particular instance of Oracle Enterprise Manager depend on the Oracle Database and Oracle Application Server versions in use. Refer to the risk matrices in the appropriate sections of this document for more information. The Critical Patch Update includes patches for Oracle Database and Oracle Application Server that can be installed to Oracle Enterprise Manager environments, and these patches should be installed.

Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne Executive Summary

This Critical Patch Update contains 3 new security fixes for Oracle PeopleSoft Enterprise PeopleTools, 1 of which may be remotely exploitable without authentication, i.e. it may be exploited over a network without the need for a username and password.
There are no new security fixes for Oracle Enterprise Portal Solutions and JD Edwards EnterpriseOne. The security patches released as part of the October 2006 Critical Patch Update should be applied if this has not been done. Please refer to Appendix A in the October 2006 Critical Patch Update advisory for more information.