CVE-2008-1817 in the critical feed json
Multiple unspecified vulnerabilities in Oracle Database 9.0.1.5 FIPS+, 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.3, and 11.1.0.6 have unknown im…
published 2008-04-16 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1817
- cvss
- 9.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in Oracle Database 9.0.1.5 FIPS+, 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.3, and 11.1.0.6 have unknown impact and remote attack vectors related to (1) SDO_IDX in the Spatial component, aka DB07; and (2) Core RDBMS, aka DB10. NOTE: the previous information was obtained from the Oracle CPU. Oracle has not commented on reliable researcher claims that DB07 is SQL injection.
Exploit prediction
1.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
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
-
securityfocus.com
/archive/1/491024/100/0/threaded
vendor-advisory
-
vupen.com
/english/advisories/2008/1267/references
vdb-entry, vendor-advisory
-
vupen.com
/english/advisories/2008/1233/references
vdb-entry, vendor-advisory
-
secunia.com
/advisories/29829
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/29874
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41858
vdb-entry
- red-database-security.com /advisory/oracle_sql_injection_sdo_idx.html
-
securitytracker.com
/id?1019855
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/42001
vdb-entry
- oracle.com /technetwork/topics/security/cpuapr2008-082075.html
-
securityfocus.com
/archive/1/490920/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/42002
vdb-entry
Sources
- CVE List CVE-2008-1817
- NVD CVE-2008-1817
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.