Skip to content
Server Security Center
KEVcritical9.8

CVE-2016-3427: Oracle Java SE and JRockit Unspecified

Oracle Java SE and JRockit · listed in the CISA catalog of actively exploited vulnerabilities since 2023-05-12.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
92%
higher than 99.8% of all CVEs
Added to CISA KEV
2023-05-12
US federal due date 2023-06-02
Ubuntu priority
medium

CVE-2016-3427 explained

CVE-2016-3427 is an unspecified vulnerability in the JMX component of Oracle Java SE, Java SE Embedded and JRockit. A remote attacker can affect confidentiality, integrity and availability. CISA lists it as known exploited, so Ubuntu systems still running the affected OpenJDK packages should be updated or upgraded.

Impact

The CVSS vector describes a network attack with low complexity. It needs no privileges and no user interaction. A successful attacker can achieve high impact on confidentiality, integrity and availability of the affected Java runtime. In practice this can mean reading data, modifying data or disrupting service. The description ties the issue to JMX-related vectors. Exposure is greatest where Java applications accept JMX connections from untrusted networks.

Who is affected

On Ubuntu 14.04 LTS, openjdk-6 is fixed in 6b39-1.13.11-0ubuntu0.14.04.1 and openjdk-7 is fixed in 7u101-2.6.6-0ubuntu0.14.04.1. On Ubuntu 16.04 LTS, openjdk-8 is fixed in 8u91-b14-0ubuntu4~16.04.1. All of these fixes are in the standard archive. Both releases are end of life. No other releases are listed in the facts.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Check which OpenJDK packages and versions are installed on each host.
  2. Update openjdk-6, openjdk-7 or openjdk-8 to at least the fixed version listed for your release.
  3. Restart all Java applications and services so they load the updated runtime.
  4. Plan upgrades from Ubuntu 14.04 LTS and 16.04 LTS to a supported release, because both are end of life.
  5. Restrict network access to JMX ports so only trusted hosts can reach them.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace openjdk-8 with the source package from the table above (this CVE affects 3 source packages).

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="openjdk-8"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="openjdk-8"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-284 Improper Access Control

Questions about CVE-2016-3427

Is this vulnerability being exploited?
Yes. CISA added CVE-2016-3427 to its Known Exploited Vulnerabilities catalog on 2023-05-12. The required action is to apply updates per vendor instructions. Known ransomware use is listed as unknown.
Do running Java applications become safe right after the package update?
No. Running Java processes keep using the old runtime code until they are restarted. Restart every affected Java service after updating the OpenJDK packages.
Our servers run Ubuntu 14.04 LTS or 16.04 LTS. Is updating enough?
Install the fixed OpenJDK packages listed for your release. Both releases are end of life, so you should also plan an upgrade to a supported release.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.