注：本文出自http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html

             檢查你的系統，是否打了最新的補丁。。。。。。。。。。。。。

Oracle Critical Patch Update Advisory - October 2017

Description

A Critical Patch Update (CPU) is a collection of patches for multiple security vulnerabilities. Critical Patch Update patches are usually cumulative, but each advisory describes only the security fixes added since the previous Critical Patch Update advisory. Thus, prior Critical Patch Update advisories should be reviewed for information regarding earlier published security fixes. Please refer to:

Oracle continues to periodically receive reports of attempts to maliciously exploit vulnerabilities for which Oracle has already released fixes. In some instances, it has been reported that attackers have been successful because targeted customers had failed to apply available Oracle patches. Oracle therefore strongly recommends that customers remain on actively-supported versions and apply Critical Patch Update fixes without delay.

This Critical Patch Update contains 252 new security fixes across the product families listed below. Please note that a MOS note summarizing the content of this Critical Patch Update and other Oracle Software Security Assurance activities is located at October 2017 Critical Patch Update: Executive Summary and Analysis

Please note that on September 22, 2017, Oracle released Security Alert for CVE-2017-9805. Customers of affected Oracle product(s) are strongly advised to apply the fixes that were announced in this Security Alert as well as those contained in this Critical Patch update

This Critical Patch Update advisory is also available in an XML format that conforms to the Common Vulnerability Reporting Format (CVRF) version 1.1. More information about Oracle's use of CVRF is available here.

Affected Products and Components

Security vulnerabilities addressed by this Critical Patch Update affect the products listed below. The product area of the patches for the listed versions is shown in the Patch Availability column corresponding to the specified Affected Products and Versions column. Please click on the link in the Patch Availability column below to access the documentation for patch availability information and installation instructions.

For an overview of the Oracle product documentation related to this Critical Patch Update, please refer to the Oracle Critical Patch Update October 2017 Documentation Map,My Oracle Support Note.

The list of affected product releases and versions that are in Premier Support or Extended Support, under the Oracle Lifetime Support Policy is as follows:

Note:

• Vulnerabilities affecting Oracle Database and Oracle Fusion Middleware may affect Oracle Fusion Applications, so Oracle customers should refer to Oracle Fusion Applications Critical Patch Update Knowledge Document, My Oracle Support Note 1967316.1 for information on patches to be applied to Fusion Application environments.
• Users running Java SE with a browser can download the latest release from http://java.com. Users on the Windows and Mac OS X platforms can also use automatic updates to get the latest release.
• Vulnerabilities affecting Oracle Solaris may affect Oracle ZFSSA so Oracle customers should refer to the Oracle and Sun Systems Product Suite Critical Patch Update Knowledge Document, My Oracle Support Note 2160904.1 for information on minimum revisions of security fixes required to resolve ZFSSA issues published in Critical Patch Updates (CPUs) and Solaris Third Party bulletins.

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 inprevious Critical Patch Update advisories. An English text version of the risk matrices provided in this document is here.

Several vulnerabilities addressed in this Critical Patch Update affect multiple products. Each vulnerability is identified by a CVE# which is a unique identifier for a vulnerability. A vulnerability that affects multiple products will appear with the same CVE# in all risk matrices. A CVE# shown in italics indicates that this vulnerability impacts a different product, but also has impact on the product where the italicized CVE# is listed.

Security vulnerabilities are scored using CVSS version 3.0 (see Oracle CVSS Scoring for an explanation of how Oracle applies CVSS version 3.0).

Oracle conducts an analysis of each security vulnerability addressed by a Critical Patch Update (CPU). Oracle does not disclose detailed information about this security analysis to customers, but the resulting Risk Matrix and associated documentation provide information about the type of vulnerability, the conditions required to exploit it, and the potential impact 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. For more information, see Oracle vulnerability disclosure policies.

The protocol in the risk matrix implies that all of its secure variants (if applicable) are affected as well. For example, if HTTP is listed as an affected protocol, it implies that HTTPS (if applicable) is also affected. The secure variant of a protocol is listed in the risk matrix only if it is the only variant affected, e.g. HTTPS will typically be listed for vulnerabilities in SSL and TLS.

Workarounds

Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible. Until you apply the CPU fixes, it may be possible to reduce the risk of successful attack by blocking 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 users that do not need the privileges 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.

Skipped Critical Patch Updates

Oracle strongly recommends that customers apply security fixes as soon as possible. For customers that have skipped one or more Critical Patch Updates and are concerned about products that do not have security fixes announced in this CPU, please review previous Critical Patch Update advisories to determine appropriate actions.

Product Dependencies

Oracle products may have dependencies on other Oracle products. Hence security vulnerability fixes announced in this Critical Patch Update may affect one or more dependent Oracle products. For details regarding these dependencies and how to apply patches to dependent products, please refer to Patch Set Update and Critical Patch Update October 2017 Availability Document, My Oracle Support Note 2296870.1.

Critical Patch Update Supported Products and Versions

Patches released through the Critical Patch Update program are provided only for product versions that are covered under the Premier Support or Extended Support phases of the Lifetime Support Policy. We recommend that customers plan product upgrades to ensure that patches released through the Critical Patch Update program are available for the versions they are currently running.

Product releases that are not under Premier Support or Extended Support are not tested for the presence of vulnerabilities addressed by this Critical Patch Update. However, it is likely that earlier versions of affected releases are also affected by these vulnerabilities. As a result, Oracle recommends that customers upgrade to supported versions.

Supported Database, Fusion Middleware, Oracle Enterprise Manager Base Platform (formerly "Oracle Enterprise Manager Grid Control") and Collaboration Suite products are patched in accordance with the Software Error Correction Support Policy explained in My Oracle Support Note 209768.1. Please review the Technical Support Policies for further guidelines regarding support policies and phases of support.

Products in Extended Support

Patches released through the Critical Patch Update program are available to customers who have Extended Support under the Lifetime Support Policy. Customers must have a valid Extended Support service contract to download patches released through the Critical Patch Update program for products in the Extended Support Phase.

Credit Statement

The following people or organizations reported security vulnerabilities addressed by this Critical Patch Update to Oracle:

• Adam Willard of Blue Canopy: CVE-2017-10360
• Alexey Tyurin of ERPScan: CVE-2017-10271
• An Anonymous researcher via Beyond Security's SecuriTeam Secure Disclosure Program: CVE-2017-10355
• Andrés Blanco of Onapsis: CVE-2017-10336
• Behzad Najjarpour Jabbari, Secunia Research at Flexera Software: CVE-2017-10051
• Charles Fol of Ambionics: CVE-2017-10362
• Christopher Tarquini: CVE-2017-10268
• Cris Neckar of Divergent Security: CVE-2017-10154
• Daniel Ekberg of Swedish Public Employment Service: CVE-2017-10321
• Daniel Fröjdendahl: CVE-2017-10293
• David Litchfield of Apple: CVE-2017-10292
• Devin Rosenbauer of Identity Works LLC: CVE-2017-10352
• Dmitrii Iudin aka @ret5et of ERPScan: CVE-2017-10373
• Fabio Pires of NCC Group: CVE-2017-10310, CVE-2017-10312
• Federico Dotta of Media Service: CVE-2017-10271
• Francesco Palmarini of Ca' Foscari University of Venice: CVE-2017-10345, CVE-2017-10356
• Gaston Traberg of Onapsis: CVE-2017-10281, CVE-2017-10332, CVE-2017-10347, CVE-2017-3444, CVE-2017-3445, CVE-2017-3446
• Hassan El Hadary - Secure Misr: CVE-2017-10363
• Jakub Palaczynski of ING Services Polska: CVE-2017-10034
• Jared McLaren of SecureWorks: CVE-2017-10259
• Jeffrey Altman of Secure Endpoints Inc.: CVE-2017-10388
• Joshua Graham of Datacom TSS: CVE-2017-10379
• José Carlos Expósito Bueno of Internet Security Auditors: CVE-2017-10163
• Juan Pablo Perez Etchegoyen of Onapsis: CVE-2017-10066, CVE-2017-10324, CVE-2017-10325, CVE-2017-10328, CVE-2017-10329, CVE-2017-10330, CVE-2017-10331, CVE-2017-10336
• loopx9: CVE-2017-10352
• Lukasz Mikula: CVE-2017-10060
• Léa Nuel of NES: CVE-2017-10055
• Marcin Wołoszyn of ING Services Polska: CVE-2017-10163, CVE-2017-10312, CVE-2017-10358, CVE-2017-10359
• Marco Squarcina of Ca' Foscari University of Venice: CVE-2017-10345, CVE-2017-10356
• Martin Doyhenard of Onapsis: CVE-2017-10322, CVE-2017-10326, CVE-2017-10332
• Mathew Nash of NCC Group: CVE-2017-10310, CVE-2017-10312
• Matias Mevied of Onapsis: CVE-2017-10323, CVE-2017-3444, CVE-2017-3445, CVE-2017-3446
• Mauro Tempesta of Ca' Foscari University of Venice: CVE-2017-10345, CVE-2017-10356
• Ming Yi Ang of SourceClear: CVE-2017-10385, CVE-2017-10391, CVE-2017-10393, CVE-2017-10400
• Nikita Egorov of ERPScan: CVE-2017-10304, CVE-2017-10306
• Orange Tsai: CVE-2017-10295
• Owais Mehtab of IS: CVE-2017-10026, CVE-2017-10259
• Reno Robert: CVE-2017-10392, CVE-2017-10407, CVE-2017-10408, CVE-2017-10428
• Riccardo Focardi of Ca' Foscari University of Venice: CVE-2017-10345, CVE-2017-10356
• Sebastian Cornejo of SIA Group: CVE-2017-10033
• Spyridon Chatzimichail of OTE Hellenic Telecommunications Organization S.A.: CVE-2017-10152
• Steven Seeley of Source Incite: CVE-2017-10309
• Tamas Szakaly: CVE-2017-10309
• Tayeeb Rana of IS: CVE-2017-10026, CVE-2017-10259
• Tobias Ospelt of modzero: CVE-2017-10356
• Tor Erling Bjorstad of Mnemonic AS: CVE-2017-10060
• Travis Emmert of Exodus Intelligence: CVE-2017-10369
• Travis Emmert of Synack Red Team: CVE-2017-10364
• Tushar Parab: CVE-2017-10159
• Vahagn Vardanyan of ERPScan: CVE-2017-10366, CVE-2017-10409, CVE-2017-10410, CVE-2017-10411, CVE-2017-10412, CVE-2017-10413, CVE-2017-10414, CVE-2017-10415, CVE-2017-10416, CVE-2017-10417
• Vicente Motos of SIA Group: CVE-2017-10033
• Zakaria Amous: CVE-2017-10261

Security-In-Depth Contributors

Oracle acknowledges people who have contributed to our Security-In-Depth program (see FAQ). People are acknowledged 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.

In this Critical Patch Update Advisory, Oracle recognizes the following for contributions to Oracle's Security-In-Depth program.:

• Andreev Ivan
• Ian Haken
• Jayson Grace of Sandia National Laboratories
• Juan Pablo Perez Etchegoyen of Onapsis
• Mohammad Abdullah - ErrOr SquaD Bangladesh
• Or Hanuka of Motorola Solutions
• Steven Danneman of Security Innovation
• Tansel ÇETİN
• Tzachy Horesh of Motorola Solutions

On-Line Presence Security Contributors

Oracle acknowledges people who have contributed to our On-Line Presence Security program (see FAQ). People are acknowledged for contributions relating to Oracle's on-line presence if they provide information, observations or suggestions pertaining to security-related issues that result in significant modification to Oracle's on-line external-facing systems.

For this quarter, Oracle recognizes the following for contributions to Oracle's On-Line Presence Security program:

• Abdelfattah Ibrahim
• Abhineeti Singh
• Adam Willard of Blue Canopy
• Ahsan Khan
• Ali Ardic
• Athul Jayaram
• Berk İmran
• Doğukan Karaciğer
• Emad Shanab of Emad Abou Shanab
• Karthik Reddy
• Krishna Manoj Vandavasi
• Lecamen Nartatez
• Muhammad Osama
• Mushraf Mustafa (3 reports)
• Pal Patel
• S. Venkatesh
• SaifAllah benMassaoud
• Teemu Kääriäinen
• Vinod Kurup
• Yassine Nafiai
• Çağatay Çalı

Critical Patch Update Schedule

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

• 16 January 2018
• 17 April 2018
• 17 July 2018
• 16 October 2018

References

• Oracle Critical Patch Updates and Security Alerts main page  [ Oracle Technology Network ]
• Critical Patch Update - October 2017 Documentation Map   [ My Oracle Support Note ]
• Oracle Critical Patch Updates and Security Alerts - Frequently Asked Questions [ CPU FAQ ]  
• Use of Common Vulnerability Scoring System (CVSS) by Oracle   [ Oracle CVSS Scoring ]
• English text version of the risk matrices   [ Oracle Technology Network ]
• List of public vulnerabilities fixed in Critical Patch Updates and Security Alerts   [ Oracle Technology Network ]

Modification History