Published on: 16 January 2019
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 5 vulnerabilities identified in Java affecting multiple sub-components including Server, ImageIO (libjepg), Networking, Deployment and Library. All of them could be remotely exploited without authentication.
For vulnerabilities identified in other Oracle products, they can be exploited by physical access or remotely through various protocols including DHCP, HTTP, HTTPS, KSSL, Local Logon, MySQL Protocol, MySQL Workbench, Oracle Net, SOAP, T3, TCP, TLS 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 submit specially crafted data to APIs in the specified Component through a web service. For other Oracle products, a remote attacker could send specially crafted network packets to the affected systems to exploit the vulnerabilities.
A complete list of the affected products can be found at:
https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.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:
https://www.oracle.com/technetwork/security-advisory/cpujan2019verbose-5072807.html
Users may contact their product support vendors for the fixes and assistance.
https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
https://www.oracle.com/technetwork/java/javase/11-0-2-relnotes-5188746.html
https://www.oracle.com/technetwork/java/javase/8u201-relnotes-5209271.html
https://www.oracle.com/technetwork/java/javase/8u202-relnotes-5209339.html
https://www.hkcert.org/my_url/en/alert/19011601
https://www.us-cert.gov/ncas/current-activity/2019/01/15/Oracle-Releases-January-2019-Security-Bulletin
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1832
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8965
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9251
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0635
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1181
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4000
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5684
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6814
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9389
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9392
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9583
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0379
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7658
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9798
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13745
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14229
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15095
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0732
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0734
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1258
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1275
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3125
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3147
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3303 (to CVE-2018-3305)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3309
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3311
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3639
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3646
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5390
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8013
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9206
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2395 (to CVE-2019-2423)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2425 (to CVE-2019-2427)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2429 (to CVE-2019-2453)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2455 (to CVE-2019-2482)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2485 (to CVE-2019-2513)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2519 (to CVE-2019-2541)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2543 (to CVE-2019-2550)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2552 (to CVE-2019-2556)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10933
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11212
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11763
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11775
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11776
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11784
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12023
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14718
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000300
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632