CVE-2012-3152
Oracle Fusion Middleware Reports Developer contains an unspecified vulnerability that allows remote attackers to affect confidentiality and integrity of affected systems.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N- blog.netinfiltration.com/2013/11/03/oracle-reports-cve-2012-3152-and-cve-2012-3153/Broken Link
- blog.netinfiltration.com/2014/01/19/upcoming-exploit-release-oracle-forms-and-reports-11g/Broken Link
- seclists.org/fulldisclosure/2014/Jan/186Mailing ListThird Party Advisory
- exploit-db.com/exploits/31253ExploitThird Party Advisory
- mandriva.com/security/advisories?name=MDVSA-2013:150Broken Link
- oracle.com/technetwork/topics/security/cpuoct2012-1515893.htmlPatchVendor Advisory
- osvdb.org/86394Broken Link
- osvdb.org/86395Broken Link
- securityfocus.com/bid/55955Broken LinkThird Party Advisory
- youtube.com/watch?v=NinvMDOj7sMExploit
- exchange.xforce.ibmcloud.com/vulnerabilities/79295Third Party AdvisoryVDB Entry
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2012-3152US Government Resource
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1638 days
- CVSS
- 9.1 CRITICAL
- EPSS (30-day exploit probability)
- 98.8% · top 1% of all CVEs
- Weakness
- NVD-CWE-noinfo
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.