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

> Remote attackers can compromise confidentiality, integrity, and availability in Oracle Java SE via unspecified JMX vectors.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 May 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Apr 2016
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-php4-mj74-f79r, MINI-4r4p-2v5h-frgv, MINI-8gv3-hp78-44rm, MINI-fhx5-4rgc-qg3c, MINI-g36q-j9fr-g6mx, MINI-prc8-548x-vvqp, MINI-q456-7pmh-jjg9, MINI-qj4j-398g-g5r8, MINI-v2qc-5wfv-jhrr, UBUNTU-CVE-2016-3427

## What is CVE-2016-3427?

CVE-2016-3427 is a critical vulnerability in Canonical Ubuntu Linux, published on 21 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-3427?

It affects 38 products.


Products: Apache Cassandra, Canonical Ubuntu Linux, Debian Debian Linux, Netapp E-Series Santricity Management Plug-Ins, Netapp E-Series Santricity Storage Manager, Netapp E-Series Santricity Web Services, Netapp Oncommand Balance, Netapp Oncommand Cloud Manager, Netapp Oncommand Insight, Netapp Oncommand Performance Manager, Netapp Oncommand Report, Netapp Oncommand Shift, Netapp Oncommand Unified Manager, Netapp Oncommand Workflow Automation, Netapp Storagegrid, Netapp Vasa Provider for Clustered Data Ontap, Netapp Virtual Storage Console, Opensuse Leap, Opensuse Opensuse, Oracle Jdk and 18 more.

## How do I fix CVE-2016-3427?

Apply the vendor's patch. US federal agencies must fix it by 2 Jun 2023.

## Is CVE-2016-3427 being exploited?

Yes. Attackers have exploited CVE-2016-3427 in the wild since at least 12 May 2023.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2018-8016](https://insights.sbomify.com/CVE-2018-8016/): Missing Authentication for Critical Function in Apache Cassandra (critical 9.8)
- [CVE-2021-44521](https://insights.sbomify.com/CVE-2021-44521/): Remote code execution for scripted UDFs (critical 9.1)
- [CVE-2026-27314](https://insights.sbomify.com/CVE-2026-27314/): Apache Cassandra: Privilege escalation via ADD IDENTITY authorization bypass (high 8.8)
- [CVE-2025-26467](https://insights.sbomify.com/CVE-2025-26467/): Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions (4.0.16 only) (high 8.8)
- [CVE-2025-23015](https://insights.sbomify.com/CVE-2025-23015/): Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3427 and fix it if it is affected.

What it is: CVE-2016-3427 is a critical vulnerability in Canonical Ubuntu Linux, published on 21 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2016-3427 in the wild since at least 12 May 2023.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-3427/ (Markdown: https://insights.sbomify.com/CVE-2016-3427/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-3427
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-3427
- OSV: https://osv.dev/vulnerability/CVE-2016-3427

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-3427/
Summaries are generated and may contain mistakes; the official description above is the record.