Threats / Oracle / CVE-2012-3152
CVE-2012-3152
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle Fusion Middleware vulnerability
Oracle Fusion Middleware Reports Developer contains an unspecified vulnerability allowing remote attackers to compromise confidentiality and integrity of affected systems.
Verdict
Today item — known-exploited.
Remote attackers can exploit this vulnerability without authentication to access sensitive data and modify system information in Oracle Fusion Middleware Reports Developer. Active exploitation in the wild indicates immediate risk.
CISA KEV Yes · 2021-11-034EPSS 0.98695 (verify live)5Exploit Weaponized · public PoC6CVSS 9.1 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.98695 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) · Affected: Oracle, Fusion Middleware. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3305 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify and access the unspecified vulnerability in Oracle Fusion Middleware Reports Developer over the network.
Business
Unauthorized remote access to reporting infrastructure creates immediate exposure of confidential business data and analytics.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract sensitive information from the Reports Developer system without proper authentication controls.
Business
Loss of data confidentiality compromises proprietary business intelligence, financial records, and customer information stored in reports.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify or corrupt report data and system configurations to alter business intelligence outputs.
Business
Integrity violations undermine decision-making accuracy, regulatory compliance, and stakeholder trust in reporting systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05