Published on: 18 April 2018
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 14 vulnerabilities identified in Java affecting multiple sub-components including AWT, Concurrency, Hotspot, Install, JAXP, JMX, Libraries, RMI, Security and Serialization. 12 of them could be remotely exploited without authentication and other vulnerabilities could affect the deployment of Java.
For vulnerabilities identified in other Oracle products, they can be exploited by physical access or remotely through various protocols including HTTP, HTTPS, NFS, LDAP, T3, TLS, MySQL protocol and XCom 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.
A complete list of the affected products can be found at:
http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
Depending on the vulnerability exploited, a successful attack could lead to denial of services, data tampering, information disclosure 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:
http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
Users may contact their product support vendors for the fixes and assistance.
http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
http://www.oracle.com/technetwork/java/javase/documentation/10u-relnotes-4108739.html
http://www.oracle.com/technetwork/java/javase/documentation/8u-relnotes-2225394.html
https://www.hkcert.org/my_url/en/alert/18041801
https://www.us-cert.gov/ncas/current-activity/2018/04/17/Oracle-Releases-April-2018-Security-Bulletin
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-1768
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-7940
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-3092
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3506
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5007
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5019
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6304
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6814
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9878
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3736
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3737
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5662
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5753
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7525
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7805
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9798
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13082
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15095
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17562
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0739
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2563
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2572
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2587
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2628
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2718
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2737 (to CVE-2018-2739)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2742
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2746 (to CVE-2018-2750)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2752 (to CVE-2018-2756)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2758 (to CVE-2018-2766)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2768 (to CVE-2018-2874)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2876 (to CVE-2018-2879)
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7489