CVE-2006-1869 in the critical feed json
Unspecified vulnerability in Oracle Database Server 8.1.7.4 and 9.0.1.5 has unknown impact and attack vectors in the Dictionary component,…
published 20y ago modified 4mo ago also EUVD-2006-1869
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.4%
- EPSS 8.4% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle Database Server 8.1.7.4 and 9.0.1.5 has unknown impact and attack vectors in the Dictionary component, aka Vuln# DB04.
Patch / fix
Is CVE-2006-1869 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
8.39% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/17590 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Technology feeds
References
-
securitytracker.com
/id?1015961
vdb-entry, patch
-
securityfocus.com
/bid/17590
vdb-entry, exploit
-
securityfocus.com
/archive/1/432267/100/0/threaded
vendor-advisory
-
secunia.com
/advisories/19712
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/19859
third-party-advisory
- oracle.com /technetwork/topics/security/cpuapr2006-090826.html
-
kb.cert.org
/vuls/id/241481
third-party-advisory, us-government-resource
-
vupen.com
/english/advisories/2006/1571
vdb-entry
-
us-cert.gov
/cas/techalerts/TA06-109A.html
third-party-advisory, us-government-resource
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26052
vdb-entry
-
vupen.com
/english/advisories/2006/1397
vdb-entry
Sources
- CVE List CVE-2006-1869
- NVD CVE-2006-1869
Fencer Intel 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.