# CVE-2012-3152: Oracle Fusion Middleware Unspecified

> Remote attackers can upload arbitrary files, including JSPs, to the Report Server, leading to arbitrary code execution and data compromise.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2012
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-x6c2-j4cw-94j8

## What is CVE-2012-3152?

CVE-2012-3152 is a critical vulnerability in Oracle Fusion Middleware, published on 16 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle Reports Developer component in Oracle Fusion Middleware 11.1.1.4, 11.1.1.6, and 11.1.2.0 allows remote attackers to affect confidentiality and integrity via unknown vectors related to Report Server Component.  NOTE: the previous information is from the October 2012 CPU. Oracle has not commented on claims from the original researcher that the URLPARAMETER functionality allows remote attackers to read and upload arbitrary files to reports/rwservlet, and that this issue occurs in earlier versions.  NOTE: this can be leveraged with CVE-2012-3153 to execute arbitrary code by uploading a .jsp file.

## Which versions are affected by CVE-2012-3152?

It affects 1 product.


Products: Oracle Fusion Middleware.

## How do I fix CVE-2012-3152?

No fix has been published for CVE-2012-3152 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2012-3152 being exploited?

Yes. Attackers have exploited CVE-2012-3152 in the wild since at least 3 Nov 2021.

Public exploit code:

- Automated exploitation scanner for Oracle Reports Server (rwservlet) — CVE-2012-3152 / CVE-2012-3153. Detects, fingerprints, reads files via LFI, tests SSRF via webhook, and uploads JSP shells. Targets Oracle Reports < 11g. For authorized use only.  (github_poc): https://github.com/abq0/rwsploit
- Oracle Forms and Reports Remote Code Execution (metasploit)
- Oracle Forms and Reports 11.1 - Arbitrary Code Execution (exploitdb)
- Oracle Forms and Reports - Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Oracle Fusion Middleware

- [CVE-2012-1710](https://insights.sbomify.com/CVE-2012-1710/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)
- [CVE-2012-0518](https://insights.sbomify.com/CVE-2012-0518/): Oracle Fusion Middleware Unspecified (medium 4.7, exploited in the wild)
- [CVE-2013-2380](https://insights.sbomify.com/CVE-2013-2380/): Other in n/a (critical 10.0)
- [CVE-2012-3135](https://insights.sbomify.com/CVE-2012-3135/): Other in n/a (critical 10.0)
- [CVE-2010-3510](https://insights.sbomify.com/CVE-2010-3510/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3152 and fix it if it is affected.

What it is: CVE-2012-3152 is a critical vulnerability in Oracle Fusion Middleware, published on 16 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2012-3152 in the wild since at least 3 Nov 2021.

Affected product: Oracle Fusion Middleware. 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-2012-3152/ (Markdown: https://insights.sbomify.com/CVE-2012-3152/index.md)
```

## Sources

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

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