# CVE-2022-21371: Path traversal in WebLogic Server

> Unauthenticated attackers can exploit a path traversal flaw in Oracle WebLogic Server to access critical data via HTTP.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2022
- **Updated:** 24 Sep 2024
- **Also known as:** CVE-2021-35685, GHSA-6rxv-546p-5g4j

## What is CVE-2022-21371?

CVE-2022-21371 is a high-severity path traversal vulnerability in Oracle Weblogic Server, published on 19 Jan 2022. 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: Web Container). Supported versions that are affected are 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 unauthenticated attacker with network access via HTTP 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-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-21371?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2022-21371?

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

## Is CVE-2022-21371 being exploited?

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

Public exploit code:

- Oracle WebLogic Server 12.1.3.0.0 / 12.2.1.3.0 / 12.2.1.4.0 / 14.1.1.0.0 Local File Inclusion (github_poc): https://github.com/Mr-xn/CVE-2022-21371
- Oracle WebLogic CVE-2022-21371 (github_poc): https://github.com/Vulnmachines/Oracle-WebLogic-CVE-2022-21371
- Oracle WebLogic Server (LFI) (github_poc): https://github.com/Cappricio-Securities/CVE-2022-21371
- Oracle WebLogic Server 14.1.1.0.0 - Local File Inclusion (exploitdb)
- Oracle WebLogic Server Local File Inclusion (nuclei): http/cves/2022/CVE-2022-21371.yaml

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

What it is: CVE-2022-21371 is a high-severity path traversal vulnerability in Oracle Weblogic Server, published on 19 Jan 2022. 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-2022-21371 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-2022-21371/ (Markdown: https://insights.sbomify.com/CVE-2022-21371/index.md)
```

## Sources

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

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