CVE-2006-0287 in the critical feed json
Unspecified vulnerability in the Oracle HTTP Server component of Oracle Database Server 10.1.0.5 and Application Server 10.1.2.0.2 has unsp…
published 20y ago modified 4mo ago also EUVD-2006-0294
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 29.0%
- EPSS 29.0% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Unspecified vulnerability in the Oracle HTTP Server component of Oracle Database Server 10.1.0.5 and Application Server 10.1.2.0.2 has unspecified impact and attack vectors, as identified by Oracle Vuln# OHS02.
Is CVE-2006-0287 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 FencerTimeline
- Published
- First public exploit (EDB-1455)
Exploit prediction
29.01% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-1455 Oracle Database Server 9i/10g - 'XML' Local Buffer Overflow local, 2006-01-26
- 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
-
securityfocus.com
/bid/16287
vdb-entry, exploit
-
secunia.com
/advisories/18493
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/18608
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24321
vdb-entry
-
vupen.com
/english/advisories/2006/0323
vdb-entry
-
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-0287
- NVD CVE-2006-0287
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.