CVE-2006-0260

Public Exploit

Description

Multiple unspecified vulnerabilities in Oracle Database server 9.2.0.7 and 10.1.0.5 have unspecified impact and attack vectors, as identified by Oracle Vuln# (1) DB05 in the (a) Data Pump component; (2) DB15 in the (b) Oracle Text component; (3) DB22 in the (c) Streams Apply component; (4) DB23 and (5) DB24 in the (d) Streams Capture component; and (6) DB26 in the (e) Streams Subcomponent. NOTE: details are unavailable from Oracle, but they have not publicly disputed a claim by a reliable independent researcher that states that DB05 involves SQL injection in the (f) LONG2VARCHAR, LONG2VCMAX, LONG2VCNT, and LONG2CLOB functions in the DBMS_METADATA_UTIL package; (g) MAKE_FILTER, FETCH_VIEWS_ERROR, FETCH_FILTERS, FETCH_VIEWS, SET_FILTER_COMMON, DO_FILTER_SCRIPT, SET_TABLE_FILTERS, and MAKE_FILTER_TEXT functions in the DBMS_METADATA_INT package; and (h) GET_PREPOST_TABLE_ACT function in the DBMS_METADATA package.

10.0

CVSS

Severity: Critical

CVSS 2.0 •

EPSS 1.35% Top 25%

Vendor Advisory secunia.com Vendor Advisory secunia.com Vendor Advisory vupen.com Vendor Advisory vupen.com

Affected: n/a n/a

References

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

Frequently Asked Questions

What is the severity of CVE-2006-0260?: CVE-2006-0260 has been scored as a critical severity vulnerability.
How to fix CVE-2006-0260?: To fix CVE-2006-0260, 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-0260 being actively exploited in the wild?: It is possible that CVE-2006-0260 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.