# CVE-2018-2894: Code injection in WebLogic Server

> Unauthenticated attackers can execute arbitrary code and take over Oracle WebLogic Server via HTTP requests.

- **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:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-h624-pqg4-29mh

## What is CVE-2018-2894?

CVE-2018-2894 is a critical code injection vulnerability in Oracle Weblogic Server, published on 18 Jul 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 - Web Services). Supported versions that are affected are 12.1.3.0, 12.2.1.2 and 12.2.1.3. Easily exploitable vulnerability allows unauthenticated 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.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-2894?

It affects 1 product.


Products: Oracle Weblogic Server.

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

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

## Is CVE-2018-2894 being exploited?

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

Public exploit code:

- CVE-2018-2894 WebLogic Unrestricted File Upload Lead To RCE Check Script (github_poc): https://github.com/LandGrey/CVE-2018-2894
- Ladon Scanner For Python, Large Network Penetration Scanner & Cobalt Strike, vulnerability / exploit / detection / MS17010/SmbGhost/CVE-2020-0796/CVE-2018-2894 (github_poc): https://github.com/k8gege/PyLadon
- Weblogic,CVE-2018-2894 (github_poc): https://github.com/jas502n/CVE-2018-2894
- cve-2018-2894 不同别人的利用方法。 (github_poc): https://github.com/111ddea/cve-2018-2894
- Oracle WebLogic Server - Remote Code Execution (nuclei): http/cves/2018/CVE-2018-2894.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-2018-2894 and fix it if it is affected.

What it is: CVE-2018-2894 is a critical code injection vulnerability in Oracle Weblogic Server, published on 18 Jul 2018. 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-2018-2894 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-2018-2894/ (Markdown: https://insights.sbomify.com/CVE-2018-2894/index.md)
```

## Sources

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

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