# CVE-2021-2109: Auth bypass in WebLogic Server

> High-privileged attackers can compromise Oracle WebLogic Server via HTTP, leading to full server takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2021
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-wx9h-q254-5w45

## What is CVE-2021-2109?

CVE-2021-2109 is a high-severity authentication bypass vulnerability in Oracle Weblogic Server, published on 20 Jan 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Console). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

## Which versions are affected by CVE-2021-2109?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2021-2109?

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

## Is CVE-2021-2109 being exploited?

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

Public exploit code:

- CVE-2021-2109 && Weblogic Server RCE via JNDI (github_poc): https://github.com/Al1ex/CVE-2021-2109
- https://github.com/rabbitsafe/CVE-2021-2109 (github_poc): https://github.com/rabbitsafe/CVE-2021-2109
- weblogic CVE-2021-2109批量验证poc (github_poc): https://github.com/yuaneuro/CVE-2021-2109_poc
- Oracle Weblogic RCE - CVE-2022-2109 (github_poc): https://github.com/Vulnmachines/oracle-weblogic-CVE-2021-2109
- Oracle WebLogic Server 14.1.1.0 - RCE (Authenticated) (exploitdb)
- CVE-2021-2109 basic scanner (github_poc): https://github.com/dinosn/CVE-2021-2109

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

What it is: CVE-2021-2109 is a high-severity authentication bypass vulnerability in Oracle Weblogic Server, published on 20 Jan 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-2109 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-2021-2109/ (Markdown: https://insights.sbomify.com/CVE-2021-2109/index.md)
```

## Sources

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

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