{"vuid":"VU#891644","idnumber":"891644","name":"Oracle Database XML Database SQL Injection vulnerability","keywords":["Oracle","Database","XML Database","Oracle CPU January 2006","oracle_cpu_january_2006","DB29"],"overview":"Oracle Database XML Database (XML DB) is vulnerable to SQL injection, possibly allowing a remote attacker to execute arbitrary SQL commands on a vulnerable Oracle installation.","clean_desc":"According to Oracle: Oracle XML DB is a feature of the Oracle Database. It provides a high-performance, native XML storage and retrieval technology. Oracle XML Database fails to properly filter user-supplied input. This may allow a remote attacker to insert arbitrary SQL commands, which may be executed by the database. We believe that this package is accessible by users with PUBLIC privileges. Based on research into public information, we believe that this issue is Oracle vuln# DB29 in the Oracle CPU for January 2006. However, there is not sufficient information to authoritatively relate Oracle vulnerability information to information provided by other parties. Note that we are aware of publicly available exploit code for this vulnerability.","impact":"A remote attacker may be able to execute SQL queries on a server, possibly with elevated privileges. As a result, attackers may be able to view or modify the contents of an Oracle database.","resolution":"Apply patches\nThis issue is corrected in the Oracle Critical Patch Update for January 2006.","workarounds":"","sysaffected":"","thanks":"This vulnerability was reported in the \nOracle Critical Patch Update for January 2006\n. Information in this document came from Oracle, Alexander Kornbrust of Red-database Security, and Integrigy.","author":"This document was written by Jeff Gennari.","public":["http://www.oracle.com/technology/deploy/security/pdf/cpujan2006.html","http://www.oracle.com/technology/oramag/oracle/04-sep/o54xml.html","http://www.red-database-security.com/advisory/oracle_cpu_jan_2006.html","http://www.integrigy.com/info/IntegrigySecurityAnalysis-CPU0106.pdf"],"cveids":["CVE-2006-0272"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2006-01-18T20:46:18Z","publicdate":"2006-01-17T00:00:00Z","datefirstpublished":"2006-01-25T21:27:43Z","dateupdated":"2006-01-27T16:54:14Z","revision":17,"vrda_d1_directreport":"0","vrda_d1_population":"3","vrda_d1_impact":"4","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"5","cam_population":"15","cam_impact":"15","cam_easeofexploitation":"7","cam_attackeraccessrequired":"10","cam_scorecurrent":"5.90625","cam_scorecurrentwidelyknown":"7.3828125","cam_scorecurrentwidelyknownexploited":"13.2890625","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":5.90625,"vulnote":null}