CVE-2006-1870 in the critical feed json
Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, 9.2.0.7, 10.1.0.5, and 10.2.0.2 has unknown impact and attack vectors…
published 2006-04-20 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1870
- cvss
- 9.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, 9.2.0.7, 10.1.0.5, and 10.2.0.2 has unknown impact and attack vectors in the Export component, aka Vuln# DB05. NOTE: details are unavailable from Oracle, but as of 20060427, they have not publicly commented on whether DB05 is the same issue as CVE-2006-2081.
Patch / fix
Exploit prediction
4.61% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 | 9.0 | AV:N/AC:L/Au:S/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, vendor-advisory
-
vupen.com
/english/advisories/2006/1571
vdb-entry, vendor-advisory
-
red-database-security.com
/advisory/oracle_cpu_apr_2006.html
vendor-advisory
-
vupen.com
/english/advisories/2006/1397
vdb-entry, vendor-advisory
- oracle.com /technetwork/topics/security/cpuapr2006-090826.html
-
kb.cert.org
/vuls/id/452681
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2006-1870
- NVD CVE-2006-1870
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.