CVE-2006-5332 in the critical feed json
Unspecified vulnerability in xdb.dbms_xdbz in the XMLDB component for Oracle Database 9.2.0.6 and 10.1.0.4 has unknown impact and remote au…
published 2006-10-18 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5317
- cvss
- 9.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.3%
- EPSS 5.3% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in xdb.dbms_xdbz in the XMLDB component for Oracle Database 9.2.0.6 and 10.1.0.4 has unknown impact and remote authenticated attack vectors, aka Vuln# DB01. NOTE: as of 20061023, Oracle has not disputed reports from reliable third parties that DB01 is for PL/SQL injection in the ENABLE_HIERARCHY_INTERNAL procedure.
Patch / fix
Exploit prediction
5.34% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Technology feeds
References
-
securityfocus.com
/bid/20588
vdb-entry, patch
-
securityfocus.com
/archive/1/449711/100/0/threaded
vendor-advisory
-
vupen.com
/english/advisories/2006/4065
vdb-entry, vendor-advisory
-
secunia.com
/advisories/22396
third-party-advisory, vendor-advisory
- red-database-security.com /advisory/oracle_cpu_oct_2006.html
- oracle.com /technetwork/topics/security/cpuoct2006-095368.html
- databasesecurity.com /oracle/OracleOct2006-CPU-Analysis.pdf
- red-database-security.com /advisory/oracle_sql_injection_dbms_xdbz0.html
-
securityfocus.com
/archive/1/449510/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/449110/100/0/threaded
mailing-list
-
kb.cert.org
/vuls/id/717140
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1017077
vdb-entry
-
us-cert.gov
/cas/techalerts/TA06-291A.html
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2006-5332
- NVD CVE-2006-5332
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.