# CVE-2023-21839: Oracle WebLogic Server Unspecified

> Unauthenticated attackers can exploit deserialization flaws in Oracle WebLogic Server to access critical data via T3 or IIOP protocols.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 1 May 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-f8x3-c29w-wfmj

## What is CVE-2023-21839?

CVE-2023-21839 is a high-severity unsafe deserialization vulnerability in Oracle Weblogic Server, published on 17 Jan 2023. 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 product of Oracle Fusion Middleware (component: Core).  Supported versions that are affected are 12.2.1.3.0, 12.2.1.4.0 and  14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Oracle WebLogic Server.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-21839?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2023-21839?

No fix has been published for CVE-2023-21839 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 22 May 2023.

## Is CVE-2023-21839 being exploited?

Yes. Attackers have exploited CVE-2023-21839 in the wild since at least 1 May 2023.

Public exploit code:

- https://github.com/DXask88MA/Weblogic-CVE-2023-21839 (github_poc): https://github.com/DXask88MA/Weblogic-CVE-2023-21839
- Weblogic CVE-2023-21839 RCE (无需Java依赖一键RCE) (github_poc): https://github.com/ASkyeye/CVE-2023-21839
- CVE-2024-20931, this is the bypass of the patch of CVE-2023-21839 (github_poc): https://github.com/dinosn/CVE-2024-20931
- CVE-2023-21839工具 (github_poc): https://github.com/Firebasky/CVE-2023-21839
- CVE-2023-21839 Python版本 (github_poc): https://github.com/houqe/POC_CVE-2023-21839
- Reproducible Docker lab for CVE-2024-21182 — Oracle WebLogic T3/IIOP OpaqueReference JNDI injection → unauthenticated RCE (CVE-2023-21839 patch-bypass family). One-command validate.sh. (github_poc): https://github.com/dinosn/CVE-2024-21182

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

What it is: CVE-2023-21839 is a high-severity unsafe deserialization vulnerability in Oracle Weblogic Server, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-21839 in the wild since at least 1 May 2023.

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

## Sources

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

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