# CVE-2018-3191: 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:** 17 Oct 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-mw7v-jjc3-g2r9

## What is CVE-2018-3191?

CVE-2018-3191 is a critical unsafe deserialization vulnerability in Oracle Weblogic Server, published on 17 Oct 2018. 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: WLS Core Components). Supported versions that are affected are 10.3.6.0, 12.1.3.0 and 12.2.1.3. 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 3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

## Which versions are affected by CVE-2018-3191?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2018-3191?

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

## Is CVE-2018-3191 being exploited?

There is no known exploitation of CVE-2018-3191 in the wild and no public exploit code.

Public exploit code:

- Weblogic-CVE-2018-3191远程代码命令执行漏洞 (github_poc): https://github.com/jas502n/CVE-2018-3191
- CVE-2018-3191 反弹shell (github_poc): https://github.com/Libraggbond/CVE-2018-3191
- https://github.com/mackleadmire/CVE-2018-3191-Rce-Exploit (github_poc): https://github.com/mackleadmire/CVE-2018-3191-Rce-Exploit
- CVE-2018-3191-PoC (github_poc): https://github.com/m00zh33/CVE-2018-3191
- CVE-2018-3191 payload generator (github_poc): https://github.com/arongmh/CVE-2018-3191

## 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-2018-3191 and fix it if it is affected.

What it is: CVE-2018-3191 is a critical unsafe deserialization vulnerability in Oracle Weblogic Server, published on 17 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3191 in the wild and no public exploit code.

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-2018-3191/ (Markdown: https://insights.sbomify.com/CVE-2018-3191/index.md)
```

## Sources

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

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