CVE-2006-0265

Public Exploit

Description

Multiple unspecified vulnerabilities in Oracle Database server 8.1.7.4, 9.0.1.5, 9.2.0.7, 10.1.0.5, and 10.2.0.1 have unspecified impact and attack vectors, as identified by Oracle Vuln# (1) DB17 in the Oracle Text component and (2) DB18 in the Program Interface Network component. NOTE: details are unavailable from Oracle, but they have not publicly disputed a claim by a reliable independent researcher that states that DB17 involves SQL injection in the (a) VALIDATE_STATEMENT and BUILD_DML functions in CTXSYS.DRILOAD; (b) CLEAN_DML function in CTXSYS.DRIDML; (c) GET_ROWID function in CTXSYS.CTX_DOC; (d) BROWSE_WORDS function in CTXSYS.CTX_QUERY; and (e) ODCIINDEXTRUNCATE, ODCIINDEXDROP, and ODCIINDEXDELETE functions in CATINDEXMETHODS.

10.0

CVSS

Severity: Critical

CVSS 2.0 •

EPSS 2.81% Top 15%

Vendor Advisory secunia.com Vendor Advisory secunia.com Vendor Advisory red-database-security.com Vendor Advisory vupen.com Vendor Advisory vupen.com

Affected: n/a n/a

References

Link	Tags
http://www.osvdb.org/22555	vdb entry
https://exchange.xforce.ibmcloud.com/vulnerabilities/24321	vdb entry
http://www.red-database-security.com/advisory/oracle_cpu_jan_2006.html	vendor advisory
http://secunia.com/advisories/18493	third party advisory vendor advisory
http://www.vupen.com/english/advisories/2006/0323	vdb entry vendor advisory
http://www.securityfocus.com/bid/16287	vdb entry exploit
http://www.osvdb.org/22640	vdb entry
http://www.kb.cert.org/vuls/id/545804	third party advisory us government resource
http://securitytracker.com/id?1015499	vdb entry patch
http://www.vupen.com/english/advisories/2006/0243	vdb entry vendor advisory
http://www.osvdb.org/22642	vdb entry
http://www.oracle.com/technetwork/topics/security/cpujan2006-082403.html
http://secunia.com/advisories/18608	third party advisory patch vendor advisory
http://www.osvdb.org/22639	vdb entry
http://www.osvdb.org/22641	vdb entry

Frequently Asked Questions

What is the severity of CVE-2006-0265?: CVE-2006-0265 has been scored as a critical severity vulnerability.
How to fix CVE-2006-0265?: To fix CVE-2006-0265, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2006-0265 being actively exploited in the wild?: It is possible that CVE-2006-0265 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~3% probability that this vulnerability will be exploited by malicious actors in the next 30 days.