# CVE-2017-3241: Deserialization in JRockit

> Unauthenticated attackers can achieve full system takeover via RMI deserialization flaws in Oracle Java SE and JRockit.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-j64j-5jrj-hggj, MINI-2wfh-wp3r-q48r, MINI-4qp4-pw5h-m779, MINI-6h92-xr2m-54mj, MINI-jx92-83m5-44h8, MINI-v3m2-qjc8-q6r6, MINI-vmpx-6pcc-7hf5, MINI-wprx-67r4-pw8h, MINI-xw6p-47q9-wwxg, UBUNTU-CVE-2017-3241

## What is CVE-2017-3241?

CVE-2017-3241 is a critical unsafe deserialization vulnerability in Oracle Jdk, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: RMI). Supported versions that are affected are Java SE: 6u131, 7u121 and 8u112; Java SE Embedded: 8u111; JRockit: R28.3.12. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, JRockit. While the vulnerability is in Java SE, Java SE Embedded, JRockit, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE, Java SE Embedded, JRockit. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS v3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-3241?

It affects 3 products.


Products: Oracle Jdk, Oracle Jre, Oracle Jrockit.

## How do I fix CVE-2017-3241?

Apply the vendor's patch.

## Is CVE-2017-3241 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3241 exists.

Public exploit code:

- POC for java RMI deserialization vulnerability (github_poc): https://github.com/xfei3/CVE-2017-3241-POC
- Oracle OpenJDK Runtime Environment 1.8.0_112-b15 - Java Serialization Denial Of Service (exploitdb)
- https://github.com/scopion/CVE-2017-3241 (github_poc): https://github.com/scopion/CVE-2017-3241

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3241 and fix it if it is affected.

What it is: CVE-2017-3241 is a critical unsafe deserialization vulnerability in Oracle Jdk, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3241 exists.

Affected product: Oracle Jdk. 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-2017-3241/ (Markdown: https://insights.sbomify.com/CVE-2017-3241/index.md)
```

## Sources

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

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