Critical Patch Update - October 2008

Microsoft October 2008 Patch Day Patches 11 Security Vulnerabilities. The patches fix four critical. Home > Windows > Microsoft October 2008 Patch Day Patches 11 Security Vulnerabilities. Oracle has released their quarterly Critical Patch Update. Shavlik Patch for Microsoft System Center. October 2008; June 2008; May 2008; April 2008; March 2008. Microsoft Security Bulletin MS08-067 - Critical. This security update is rated Critical for all supported editions of Microsoft Windows 2000.

CPUOct. 20. 08 Advisory. 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. Critical Patch Updates are cumulative, except as noted below, but each advisory describes only the security fixes added since the previous Critical Patch Update.

• 11 updates to be issued by Microsoft in October's monthly patch release: 4 critical. Bulletin; Blog; Four critical updates this Patch Tuesday Posted by Virus Bulletin on Oct 14. Posted on 14 October 2008 by Virus Bulletin.
• Appendix A - Oracle Database. Oracle Database Executive Summary. This Critical Patch Update contains 15 new security fixes for the Database Suite. 1 of these vulnerabilities may be remotely exploitable without authentication.

Thus, prior Critical Patch Update Advisories should be reviewed for information regarding earlier accumulated security fixes. Please refer to. Critical Patch Updates and Security Alerts for information about Oracle Security Advisories. Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply fixes as soon as possible. This Critical Patch Update contains 3. 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 .

Please click on the link in . No products in this category are affected by the fixes included in this Critical Patch Update. Category IIIProducts 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.

Patch Availability Table and Risk Matrices. The Oracle Database, Oracle Application Server, Oracle Enterprise Manager Grid Control, Oracle E- Business Suite Applications (Release 1.

JD Edwards Enterprise. One, JD Edwards One.

World Tools, People. Soft Enterprise Portal Applications, People.

Soft Enterprise People. Tools and Siebel Enterprise patches in the Updates are cumulative; patches for any product included in a Critical Patch Update will include all fixes for that product from the previous Critical Patch Updates. Oracle E- Business Suite Applications Release 1. Oracle E- Business Suite Applications customers should refer to previous Critical Patch Updates to identify previous security fixes they want to apply.

Oracle Collaboration Suite patches were cumulative up to and including the fixes provided in the July 2. Critical Patch Update. From the July 2. 00. Critical Patch Update on, Oracle Collaboration Suite security fixes are delivered using the one- off patch infrastructure normally used by Oracle to deliver single bug fixes to customers. Patches for BEA products are not cumulative (unless otherwise stated), so BEA customers should refer to previous Security Advisories to identify previous security 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 October 2. Documentation Map, Meta. Link Note 7. 38. 89.

Risk Matrix Content. Risk matrices list only security vulnerabilities that are newly fixed by the patches associated with this advisory. Risk matrices for previous security 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. Security vulnerabilities are scored using CVSS version 2. Oracle CVSS Scoring for an explanation of how Oracle applies CVSS 2.

Oracle conducts an analysis of each security vulnerability addressed by a Critical Patch Update (CPU). Oracle does not disclose information about the security analysis, but the resulting Risk Matrix and associated documentation provide information about the type of vulnerability, the conditions required to exploit it, and the potential 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 CPUs or Security Alerts to individual customers. Finally, Oracle does not distribute exploit code or “proof- of- concept” code for product vulnerabilities. Starting in the July 2. Critical Patch Update, Oracle uses Common Vulnerabilities and Exposures ( CVE) identifiers rather than Oracle proprietary identifiers for identifying vulnerabilities (Vuln#) in Risk Matrices (see FAQ). Common Vulnerabilities and Exposures maintains a dictionary of CVE Identifiers for publicly known security vulnerabilities. Workarounds. Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply fixes as soon as possible.

Until you apply the CPU fixes, 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 unprivileged users may help reduce the risk of successful attack. Both approaches may break application functionality, so Oracle strongly recommends that customers test changes 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. Critical Patch Update patches are not provided for product versions that are no longer covered under the Premier Support or Extended Support phases of the Lifetime Support Policy. We recommend that customers upgrade to the latest supported version of Oracle products in order to obtain patches.

Extended Support Phase: Critical Patch Update patches are available to customers who have purchased Extended Support under the Lifetime Support Policy. Customers must have a valid Extended Support service contract to be able to download Critical Patch Update patches for products in the Extended Support Phase.

Critical Patch Update patches may not be downloaded to update products supported with Sustaining Support, or to update any unsupported products. Supported Database, Fusion Middleware and Collaboration Suite products are patched in accordance with the Software Error Correction Support Policy explained in Meta. Link Note 2. 09. 76. Please review the Technical Support Policies for further guidelines regarding support policies and phases of support.

On Request Model for Oracle Database and Oracle Application Server. Oracle will proactively create patches only for platform/version combinations that, based on historical data, customers are likely to download for the next Critical Patch Update. We create patches for historically inactive platform/version combinations of the Oracle Database and Oracle Application Server only if requested by customers. Fixes for the vulnerabilities will continue to be included in future releases and patch sets. Additional details regarding the products, versions and platforms that will be supported for the next Critical Patch Update and the process for requesting On Request patches are available in the Critical Patch Update October 2. Availability Information for Oracle Database and Fusion Middleware Products ( Meta.

Link Note 7. 35. 21. Credit Statement. The following people or organizations discovered and brought security vulnerabilities addressed by this Critical Patch Update to Oracle's attention: Joshua J. Drake of i. Defense; Esteban Martinez Fayo of Application Security, Inc.; Pete Finnigan; Tony Fogarty of DNV; guyp of Sentrigo; Jack Kanter of Integrigy; Joxean Koret; Alexander Kornbrust of Red Database Security; Sean Larsson of i. Defense; Slavik Markovich of Sentrigo; Amichai Shulman of Imperva, Inc.; and Chris Valasek of IBM Corp. Security- In- Depth Contributors.

Oracle provides recognition to people that have contributed to our Security- In- Depth program (see FAQ). People are recognized for Security- In- Depth contributions if they provide information, observations or suggestions pertaining to security vulnerability issues that result in significant modification of Oracle code or documentation in future releases, but are not of such a critical nature that they are distributed in Critical Patch Updates. For this Critical Patch Update, Oracle recognizes Chris Anley of NGS Software; Jeff Kayser of Jibe Consulting; David Litchfield of NGS Software; Joshua Tolley of Partnet Inc. The next four dates are: 1.

January 2. 00. 91. April 2. 00. 91. 4 July 2. October 2. 00. 9References.

Modification History. Sep- 0. 3Rev 3. Change date of CPUOct. Oct- 1. 5Rev 2. Corrected Credit Statement to include Joshua J. Drake of i. Defense and Sean Larsson of i.

Defense. 20. 08- Oct- 1. Rev 1. Initial Release.

Appendix A - Oracle Database. Oracle Database Executive Summary. This Critical Patch Update contains 1.

Database Suite. Please see Critical Patch Update for July 2. Times Ten In- Memory Database.

Oracle HTTP Server, which is installed by default with Oracle Database 9i Release 2. For Oracle Database versions 1.