CVE-2006-0269 json
Unspecified vulnerability in the Streams Capture component of Oracle Database server 10.1.0.5 and 10.2.0.1 has unspecified impact and attac…
published 2006-01-18 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0276
- cvss
- 5.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Streams Capture component of Oracle Database server 10.1.0.5 and 10.2.0.1 has unspecified impact and attack vectors, as identified by Oracle Vuln# DB25. NOTE: details are unavailable from Oracle, but they have not publicly disputed a claim by a reliable independent researcher that states that the problem is SQL injection in the SET_DIRECTORY_ROOT function in the DBMS_CDC_PUBLISH package.
Exploit prediction
2.00% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
secunia.com
/advisories/18493
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2006/0323
vdb-entry, vendor-advisory
-
vupen.com
/english/advisories/2006/0243
vdb-entry, vendor-advisory
-
secunia.com
/advisories/18608
third-party-advisory, vendor-advisory
-
osvdb.org
/22563
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24321
vdb-entry
- red-database-security.com /advisory/oracle_cpu_jan_2006.html
-
securityfocus.com
/bid/16287
vdb-entry
-
kb.cert.org
/vuls/id/545804
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1015499
vdb-entry
- oracle.com /technetwork/topics/security/cpujan2006-082403.html
Sources
- CVE List CVE-2006-0269
- NVD CVE-2006-0269
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.