# CVE-2017-3248: Deserialization in WebLogic Server

> Unauthenticated attackers can achieve remote code execution and full server takeover via the T3 protocol in Oracle WebLogic Server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** No
- **Published:** 27 Jan 2017
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-j377-ff8h-jf66

## What is CVE-2017-3248?

CVE-2017-3248 is a critical unsafe deserialization vulnerability in Oracle Weblogic Server, 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 Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Core Components). Supported versions that are affected are 10.3.6.0, 12.1.3.0, 12.2.1.0 and 12.2.1.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS v3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts).

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

It affects 1 product.


Products: Oracle Weblogic Server.

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

No fix has been published for CVE-2017-3248 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3248 being exploited?

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

Public exploit code:

- weblogic 漏洞扫描工具。目前包含对以下漏洞的检测能力：CVE-2014-4210、CVE-2016-0638、CVE-2016-3510、CVE-2017-3248、CVE-2017-3506、CVE-2017-10271、CVE-2018-2628、CVE-2018-2893、CVE-2018-2894、CVE-2018-3191、CVE-2018-3245、CVE-2018-3252、CVE-2019-2618、CVE-2019-2725、CVE-2019-2729、CVE-2019-2890、CVE-2020-2551、CVE-2020-14750、CVE-2020-14882、CVE-2020-14883 (github_poc): https://github.com/daybreak-kits/weblogicScanner
- Oracle Weblogic Server Deserialization RCE - RMI UnicastRef (metasploit)
- Oracle WebLogic 12.1.2.0 - RMI Registry UnicastRef Object Java Deserialization Remote Code Execution (exploitdb)
- CVE-2017-3248 (github_poc): https://github.com/ianxtianxt/CVE-2017-3248
- https://github.com/BabyTeam1024/CVE-2017-3248 (github_poc): https://github.com/BabyTeam1024/CVE-2017-3248

## Other vulnerabilities in Oracle Weblogic Server

- [CVE-2020-14750](https://insights.sbomify.com/CVE-2020-14750/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14882](https://insights.sbomify.com/CVE-2020-14882/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14644](https://insights.sbomify.com/CVE-2020-14644/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-2883](https://insights.sbomify.com/CVE-2020-2883/): Oracle WebLogic Server Unspecified (critical 9.8, exploited in the wild)
- [CVE-2020-2551](https://insights.sbomify.com/CVE-2020-2551/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3248 is a critical unsafe deserialization vulnerability in Oracle Weblogic Server, 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-3248 exists.

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

## Sources

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

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