Loading vulnerability…
An unspecified vulnerability exists in the Workspace Manager component of Oracle Database versions 10.2.0.4 and 11.1.0.6. The vulnerability allows remote authenticated users to impact confidentiality and integrity through unknown attack vectors. This issue is distinct from CVE-2009-0975.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module targeting a SQL injection vulnerability (CVE-2009-0978) in the Oracle Database SYS.LT.ROLLBACKWORKSPACE procedure. The exploit allows an attacker with EXECUTE privileges on the SYS.LT package to execute arbitrary SQL statements, such as granting DBA privileges to the current user. The module constructs and injects a malicious PL/SQL function and leverages both CREATEWORKSPACE and ROLLBACKWORKSPACE procedures to trigger the payload. The exploit is operational and can be used for privilege escalation or arbitrary SQL execution on vulnerable Oracle databases. The code is written in Ruby and is structured as a standard Metasploit module.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.