Threats / Oracle / CVE-2016-3427
CVE-2016-3427
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle Java SE and JRockit vulnerability
Oracle Java SE and JRockit contain an unspecified vulnerability in Java Management Extensions (JMX) allowing remote attackers to compromise confidentiality, integrity, and availability through multiple attack vectors including sandboxed app
Verdict
Today item — known-exploited.
Remote attackers can exploit JMX functionality in Java SE and JRockit to achieve unauthorized access and system compromise. The vulnerability affects both sandboxed execution contexts and direct API consumption, creating broad exploitation surface.
CISA KEV Yes · 2023-05-124EPSS 0.92334 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-05-12).
Probability (EPSS)
EPSS 0.92334 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Oracle, Java SE and JRockit. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2577 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious Java applet or Web Start application that exploits the JMX vulnerability to break out of sandbox restrictions.
Business
Attackers gain code execution within user browsers and client systems, enabling data theft and malware installation.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send specially crafted data to exposed JMX APIs or web service endpoints that consume Java SE or JRockit components.
Business
Backend systems become compromised, allowing attackers to manipulate application logic, access sensitive data, or disrupt service availability.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the compromised JMX interface to escalate privileges and move laterally within the enterprise network.
Business
Organizational infrastructure suffers widespread compromise affecting confidentiality of proprietary information and integrity of critical systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05