CVE-2006-0263 in the critical feed json
Multiple unspecified vulnerabilities in Oracle Database server 8.1.7.4, 9.0.1.5, 9.0.1.5 FIPS, 9.2.0.7, 10.1.0.5, and 10.2.0.1 have unspeci…
published 20y ago modified 4mo ago also EUVD-2006-0270
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.5%
- EPSS 7.5% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in Oracle Database server 8.1.7.4, 9.0.1.5, 9.0.1.5 FIPS, 9.2.0.7, 10.1.0.5, and 10.2.0.1 have unspecified impact and attack vectors, as identified by Oracle Vuln# (1) DB09 in the (a) Net Listener component; and (2) DB12 and (3) DB13 in the Network Communications (RPC) component.
Is CVE-2006-0263 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
7.46% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-14).
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
-
secunia.com
/advisories/18493
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/18608
third-party-advisory, vendor-advisory
-
osvdb.org
/22550
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24321
vdb-entry
-
osvdb.org
/22551
vdb-entry
-
osvdb.org
/22547
vdb-entry
-
vupen.com
/english/advisories/2006/0323
vdb-entry
-
securityfocus.com
/bid/16287
vdb-entry
-
kb.cert.org
/vuls/id/870172
third-party-advisory, us-government-resource
-
us-cert.gov
/cas/techalerts/TA06-018A.html
third-party-advisory, us-government-resource
-
kb.cert.org
/vuls/id/545804
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1015499
vdb-entry
-
vupen.com
/english/advisories/2006/0243
vdb-entry
- oracle.com /technetwork/topics/security/cpujan2006-082403.html
Sources
- CVE List CVE-2006-0263
- NVD CVE-2006-0263
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.