Loading vulnerability…
CVE-2008-3979 is a SQL injection vulnerability in the MDSYS.SDO_TOPO_DROP_FTBL trigger of the Oracle Spatial component in Oracle Database 10g R1 (10.1.0.5) and R2 (10.2.0.2). The vulnerability allows a low-privileged, authenticated user with only CREATE SESSION privileges to inject arbitrary SQL via the trigger, leading to privilege escalation and execution of actions as the MDSYS user. The flaw is due to unsafe dynamic SQL construction in the trigger when a table is dropped, where user-controlled input is embedded in a SQL query without proper sanitization.
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 (1 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/sqli/oracle/droptable_trigger.rb) that exploits a SQL injection vulnerability (CVE-2008-3979) in the Oracle Database MDSYS.SDO_TOPO_DROP_FTBL trigger. The module generates a SQL file (msf.sql) containing base64-encoded PL/SQL code that, when executed on a vulnerable Oracle database, escalates the privileges of a specified user to MDSYS and then to DBA by creating a malicious trigger in the system schema. The exploit is a two-stage attack: first, it leverages the SQL injection to execute arbitrary SQL as MDSYS, and second, it abuses the 'CREATE ANY TRIGGER' privilege to escalate to DBA. The module is operational and requires the attacker to have access to the target Oracle database. The main attack vector is network-based, targeting the database service. The repository is structured as a typical Metasploit module, with all exploit logic contained in a single Ruby file.
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.