CVE-2006-2505 json
Oracle Database Server 10g Release 2 allows local users to execute arbitrary SQL queries via a reference to a malicious package in the TYPE…
published 2006-05-22 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2505
- cvss
- 3.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 2
- Exploit-DB
Summary
Oracle Database Server 10g Release 2 allows local users to execute arbitrary SQL queries via a reference to a malicious package in the TYPE_NAME argument in the (1) GET_DOMAIN_INDEX_TABLES or (2) GET_V2_DOMAIN_INDEX_TABLES function in the DBMS_EXPORT_EXTENSION package.
Timeline
- First public exploit (EDB-1719)
- Published
Exploit prediction
2.50% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-3269 Oracle 9i/10g - DBMS_EXPORT_EXTENSION SQL Injection remote, 2007-02-05
- EDB-1719 Oracle 10g Release 2 - 'DBMS_EXPORT_EXTENSION' SQL local, 2006-04-26
- secunia.com http://secunia.com/advisories/19860 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/17699 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.6 | AV:L/AC:L/Au:N/C:N/I:P/A:P |
Classification
- Technology feeds
References
-
secunia.com
/advisories/19860
third-party-advisory, exploit, vendor-advisory
-
securityfocus.com
/bid/17699
vdb-entry, exploit
-
securityfocus.com
/archive/1/432078/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/432354/100/0/threaded
mailing-list
-
kb.cert.org
/vuls/id/932124
third-party-advisory, us-government-resource
-
securityfocus.com
/archive/1/432355/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-2505
- NVD CVE-2006-2505
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.