CVE-2016-3427
Oracle Java SE and JRockit Unspecified Vulnerability
Oracle Java SE and JRockit
Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77; Java SE Embedded 8u77; and JRockit R28.3.9 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 12 May 2023. US federal agencies were required to remediate it by 2 June 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 92.3%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2016-3427 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2016-3427.
What does CVE-2016-3427 affect?
CVE-2016-3427 affects Oracle Java SE and JRockit. Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77; Java SE Embedded 8u77; and JRockit R28.3.9 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX.
How severe is CVE-2016-3427?
CVE-2016-3427 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 92.3%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 June 2023.
How should organisations respond to CVE-2016-3427?
Apply the vendor patch for Oracle Java SE and JRockit as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.