CVE-2008-3979 json
Unspecified vulnerability in the Oracle Spatial component in Oracle Database 10.1.0.5 and 10.2.0.2 allows remote authenticated users to aff…
published 2009-01-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3964
- cvss
- 5.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.4%
- EPSS 32.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Unspecified vulnerability in the Oracle Spatial component in Oracle Database 10.1.0.5 and 10.2.0.2 allows remote authenticated users to affect confidentiality and integrity via unknown vectors. NOTE: the previous information was obtained from the January 2009 CPU. Oracle has not commented on reliable researcher claims that this issue is a SQL injection vulnerability that allows remote authenticated users to gain MDSYS privileges via the MDSYS.SDO_TOPO_DROP_FTBL trigger.
Timeline
- First public exploit (Metasploit auxiliary/sqli/oracle/droptable_trigger)
- Published
Exploit prediction
32.43% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/sqli/oracle/droptable_trigger Oracle DB SQL Injection in MDSYS.SDO_TOPO_DROP_FTBL Trigger metasploit auxiliary, normal rank, 2009-01-13
- EDB-8074 Oracle 10g - MDSYS.SDO_TOPO_DROP_FTBL SQL Injection (Metasploit) local, 2009-02-18
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
References
-
exploit-db.com
/exploits/8074
exploit
-
secunia.com
/advisories/33525
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/0115
vdb-entry, vendor-advisory
-
osvdb.org
/51354
vdb-entry
-
securitytracker.com
/id?1021561
vdb-entry
- oracle.com /technetwork/topics/security/cpujan2009-097901.html
-
securityfocus.com
/bid/33177
vdb-entry
-
securityfocus.com
/archive/1/500061/100/0/threaded
mailing-list
Sources
- CVE List CVE-2008-3979
- NVD CVE-2008-3979
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.