CVE-2006-1870
published 2006-04-20CVE-2006-1870: Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, 9.2.0.7, 10.1.0.5, and 10.2.0.2 has unknown impact and attack vectors in the Export…
critical9CVSS 3.1
AVNACLAuSCCICAC
Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, 9.2.0.7, 10.1.0.5, and 10.2.0.2 has unknown impact and attack vectors in the Export component, aka Vuln# DB05. NOTE: details are unavailable from Oracle, but as of 20060427, they have not publicly commented on whether DB05 is the same issue as CVE-2006-2081.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| oracle | database_server | — | — |
| oracle | database_server | — | — |
| oracle | database_server | — | — |
| oracle | database_server | — | — |
| oracle | database_server | — | — |
GHSA
GHSA-7jg3-5w3h-9634: Unspecified vulnerability in Oracle Database Server 8
ghsa_unreviewed·2022-05-01·CVSS 4.6
CVE-2006-1870 [MEDIUM] GHSA-7jg3-5w3h-9634: Unspecified vulnerability in Oracle Database Server 8
Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, 9.2.0.7, 10.1.0.5, and 10.2.0.2 has unknown impact and attack vectors in the Export component, aka Vuln# DB05. NOTE: details are unavailable from Oracle, but as of 20060427, they have not publicly commented on whether DB05 is the same issue as CVE-2006-2081.
GHSA
GHSA-3r8p-382h-8p7p: Oracle Database Server 10g Release 2 allows local users to execute arbitrary SQL queries via the GET_DOMAIN_INDEX_METADATA function in the DBMS_EXPORT
ghsa_unreviewed·2022-05-01·CVSS 9.0
CVE-2006-2081 [CRITICAL] GHSA-3r8p-382h-8p7p: Oracle Database Server 10g Release 2 allows local users to execute arbitrary SQL queries via the GET_DOMAIN_INDEX_METADATA function in the DBMS_EXPORT
Oracle Database Server 10g Release 2 allows local users to execute arbitrary SQL queries via the GET_DOMAIN_INDEX_METADATA function in the DBMS_EXPORT_EXTENSION package. NOTE: this issue was originally linked to DB05 (CVE-2006-1870), but a reliable third party has claimed that it is not the same issue. Based on details of the problem, the primary issue appears to be insecure privileges that facilitate the introduction of SQL in a way that is not related to special characters, so this is not "SQL injection" per se.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://secunia.com/advisories/19712http://secunia.com/advisories/19859http://securitytracker.com/id?1015961http://www.kb.cert.org/vuls/id/452681http://www.oracle.com/technetwork/topics/security/cpuapr2006-090826.htmlhttp://www.red-database-security.com/advisory/oracle_cpu_apr_2006.htmlhttp://www.securityfocus.com/archive/1/432267/100/0/threadedhttp://www.securityfocus.com/bid/17590http://www.vupen.com/english/advisories/2006/1397http://www.vupen.com/english/advisories/2006/1571http://secunia.com/advisories/19712http://secunia.com/advisories/19859http://securitytracker.com/id?1015961http://www.kb.cert.org/vuls/id/452681http://www.oracle.com/technetwork/topics/security/cpuapr2006-090826.htmlhttp://www.red-database-security.com/advisory/oracle_cpu_apr_2006.htmlhttp://www.securityfocus.com/archive/1/432267/100/0/threadedhttp://www.securityfocus.com/bid/17590http://www.vupen.com/english/advisories/2006/1397http://www.vupen.com/english/advisories/2006/1571
2006-04-20
Published