# CVE-2019-2729: Auth bypass in WebLogic Server

> Unauthenticated attackers can compromise Oracle WebLogic Server via HTTP, leading to full system takeover.

- **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:** 19 Jun 2019
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-hmxx-vvw4-43vc

## What is CVE-2019-2729?

CVE-2019-2729 is a critical authentication bypass vulnerability in Oracle Communications Diameter Signaling Router, published on 19 Jun 2019. 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: Web Services). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0 and 12.2.1.3.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 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).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2019-2729?

It affects 9 products.


Products: Oracle Communications Diameter Signaling Router, Oracle Communications Network Integrity, Oracle Hyperion Infrastructure Technology, Oracle Identity Manager, Oracle Peoplesoft Enterprise Peopletools, Oracle Rapid Planning, Oracle Storagetek Tape Analytics Sw Tool, Oracle Tape Library Acsls, Oracle Weblogic Server.

## How do I fix CVE-2019-2729?

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

## Is CVE-2019-2729 being exploited?

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

Public exploit code:

- CVE-2019-2729 Exploit Script (github_poc): https://github.com/ruthlezs/CVE-2019-2729-Exploit
- Exploit code for CVE-2019-2729 (github_poc): https://github.com/waffl3ss/CVE-2019-2729
- python3 POC for CVE-2019-2729 WebLogic Deserialization Vulnerability and CVE-2017-10271 amongst others (github_poc): https://github.com/pizza-power/weblogic-CVE-2019-2729-POC
- PoC for exploiting CVE-2019-2729 on WebLogic (github_poc): https://github.com/Luchoane/CVE-2019-2729_creal
- Oracle Weblogic 10.3.6.0.0 - Remote Command Execution (exploitdb)
- Oracle WebLogic Server Administration Console - Remote Code Execution (nuclei): http/cves/2019/CVE-2019-2729.yaml

## Other vulnerabilities in Oracle Communications Diameter Signaling Router

- [CVE-2017-9841](https://insights.sbomify.com/CVE-2017-9841/): PHPUnit Command Injection (critical 9.8, exploited in the wild)
- [CVE-2019-2399](https://insights.sbomify.com/CVE-2019-2399/): Information disclosure in Communications Diameter Signaling Router (DSR) (medium 6.5)
- [CVE-2020-14788](https://insights.sbomify.com/CVE-2020-14788/): Cross-site scripting in Communications Diameter Signaling Router (DSR) (medium 6.1)
- [CVE-2020-14787](https://insights.sbomify.com/CVE-2020-14787/): Cross-site scripting in Communications Diameter Signaling Router (DSR) (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2729 and fix it if it is affected.

What it is: CVE-2019-2729 is a critical authentication bypass vulnerability in Oracle Communications Diameter Signaling Router, published on 19 Jun 2019. 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-2019-2729 exists.

Affected product: Oracle Communications Diameter Signaling Router. 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-2019-2729/ (Markdown: https://insights.sbomify.com/CVE-2019-2729/index.md)
```

## Sources

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

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