# CVE-2019-2904: Auth bypass in Enterprise Repository

> Unauthenticated attackers can compromise Oracle JDeveloper and ADF 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:** 16 Oct 2019
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-c5wp-xqq4-5j7g

## What is CVE-2019-2904?

CVE-2019-2904 is a critical authentication bypass vulnerability in Oracle Application Testing Suite, published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle JDeveloper and ADF product of Oracle Fusion Middleware (component: ADF Faces). Supported versions that are affected are 11.1.1.9.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 JDeveloper and ADF. Successful attacks of this vulnerability can result in takeover of Oracle JDeveloper and ADF. 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-2019-2904?

It affects 22 products.


Products: Oracle Application Testing Suite, Oracle Banking Enterprise Collections, Oracle Banking Enterprise Originations, Oracle Banking Enterprise Product Manufacturing, Oracle Banking Platform, Oracle Business Process Management Suite, Oracle Clinical, Oracle Communications Diameter Signaling Router, Oracle Communications Network Integrity, Oracle Communications Service Broker, Oracle Communications Services Gatekeeper, Oracle Enterprise Repository, Oracle Financial Services Lending and Leasing, Oracle Financial Services Revenue Management and Billing Analytics, Oracle Flexcube Private Banking, Oracle Health Sciences Data Management Workbench, Oracle Hyperion Planning, Oracle Rapid Planning, Oracle Retail Assortment Planning, Oracle Retail Clearance Optimization Engine and 2 more.

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

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

## Is CVE-2019-2904 being exploited?

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

## Other vulnerabilities in Oracle Application Testing Suite

- [CVE-2026-35290](https://insights.sbomify.com/CVE-2026-35290/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2026-46876](https://insights.sbomify.com/CVE-2026-46876/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2026-46924](https://insights.sbomify.com/CVE-2026-46924/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2018-1275](https://insights.sbomify.com/CVE-2018-1275/): Spring Framework has Improperly Implemented Security Check for Standard (critical 9.8)
- [CVE-2026-70862](https://insights.sbomify.com/CVE-2026-70862/): Missing authorization in Oracle Application Testing Suite (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2904 is a critical authentication bypass vulnerability in Oracle Application Testing Suite, published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-2904 in the wild and no public exploit code.

Affected product: Oracle Application Testing Suite. 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-2904/ (Markdown: https://insights.sbomify.com/CVE-2019-2904/index.md)
```

## Sources

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

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