Published on: 21 July 2016
Oracle has released Critical Patch Update (CPU) Advisory with collections of patches for multiple security vulnerabilities found in Java SE and various Oracle products.
There are 13 vulnerabilities identified in Java affecting multiple sub-components including CORBA, Deployment, Hotspot, Install, JavaFX, JAXP, Libraries and Networking. All of them could be remotely exploited without authentication in which 3 of them could affect server deployment of Java (e.g. through a web service).
For vulnerabilities identified in those Oracle products, they can be remotely exploited through various protocols including HTTP, HTTPS, IPMI, MySQL Protocol, NTP, Oracle Net, SNMP, SSH, SSL/TLS, T3, TLS, UDP and X11 over a network.
There are multiple attack vectors. For Java, an attacker could entice a user to open a specially crafted web page containing un-trusted Java applet or Java Web Start application with malicious content, or to launch executables using the Java launcher. For other Oracle products, a remote attacker could send specially crafted network packets to the affected system to exploit the vulnerabilities.
Oracle Java SE
Database Server
Oracle Linux and Virtualization
Oracle MySQL Product Suite
Fusion Applications and Middleware
E-Business Suite
Enterprise Manager
Health Sciences
JD Edwards
Oracle Banking Platform
Oracle Communications Applications
Oracle Financial Services Applications
Oracle Insurance Applications
Oracle Knowledge Applications
Oracle Policy Automation
Oracle Primavera Products Suite
Oracle Supply Chain Products
Oracle Utilities Applications
Oracle and Sun Systems Products Suite
PeopleSoft
Retail Applications
Siebel CRM
Depending on the vulnerability exploited, a successful attack could lead to arbitrary code execution, denial of services, information disclosure, bypass of security restrictions or compromise of a vulnerable system.
Patches for affected systems are available. Users of the affected systems should follow the recommendations provided by the product vendor and take immediate actions to mitigate the risk.
For Oracle Java SE products, please refer to the following link:
For other Oracle products, please refer to the section "Patch Availability Table and Risk Matrices" of corresponding security advisory at the vendor’s website:
Users may contact their product support vendors for the fixes and assistance.
http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html
http://www.oracle.com/technetwork/java/javase/8u101-relnotes-3021761.html
http://www.oracle.com/technetwork/java/javase/8u102-relnotes-3021767.html
https://www.hkcert.org/my_url/en/alert/16072001
https://www.us-cert.gov/ncas/current-activity/2016/07/19/Oracle-Releases-Security-Bulletin
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-3137
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-3410
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2064
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2566
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3571
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9708
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0204
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0228
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0235
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1791
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1793
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3183
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3197
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3237
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3253
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5300
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5600
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7182
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7501
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8104
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0635
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0702
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0800
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1181
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1548
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2105
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2107
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3081
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3424
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3432
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3433
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3440
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3444 (to CVE-2016-3446)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3448
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3450 (to CVE-2016-3453)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3458 (to CVE-2016-3459)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3467 (to CVE-2016-3472)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3474 (to CVE-2016-3491)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3493 (to CVE-2016-3494)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3496 (to CVE-2016-3504)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3506 (to CVE-2016-3550)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3552 (to CVE-2016-3561)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3563 (to CVE-2016-3598)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3606 (to CVE-2016-3615)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5436 (to CVE-2016-5437)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5439 (to CVE-2016-5477)