CVE-2006-0283 in the critical feed json
Unspecified vulnerability in Oracle Database Server 10.1.0.4.2, Application Server 10.1.2.0.2, and Collaboration Suite Release 2, version 9…
published 2006-01-18 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0290
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.5%
- EPSS 6.5% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle Database Server 10.1.0.4.2, Application Server 10.1.2.0.2, and Collaboration Suite Release 2, version 9.0.4.2 (Oracle9i) has unspecified impact and attack vectors, as identified by Oracle Vuln# DBC02 in the Reorganize Objects & Convert Tablespace component.
Patch / fix
- securitytracker.com/id?1015499 patch
- secunia.com/advisories/18608 advisory
Exploit prediction
6.53% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/16287 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?1015499
vdb-entry, patch
-
secunia.com
/advisories/18608
third-party-advisory, patch, vendor-advisory
-
securityfocus.com
/bid/16287
vdb-entry, exploit
-
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
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24321
vdb-entry
-
kb.cert.org
/vuls/id/545804
third-party-advisory, us-government-resource
- oracle.com /technetwork/topics/security/cpujan2006-082403.html
Sources
- CVE List CVE-2006-0283
- NVD CVE-2006-0283
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.