CVE-2006-1874 json
Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, and 9.2.0.6 has unknown impact and attack vectors in the Oracle Spati…
published 2006-04-20 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1874
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle Database Server 8.1.7.4, 9.0.1.5, and 9.2.0.6 has unknown impact and attack vectors in the Oracle Spatial component, aka Vuln# DB09. NOTE: Oracle has not disputed reliable claims that this issue is SQL injection in MDSYS.PRVT_IDX using the (1) EXECUTE_INSERT, (2) EXECUTE_DELETE, (3) EXECUTE_UPDATE, (4) EXECUTE UPDATE, and (5) CRT_DUMMY functions.
Exploit prediction
3.99% chance of exploitation in the next 30 days, higher than 90% 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 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
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
-
vupen.com
/english/advisories/2006/1397
vdb-entry, vendor-advisory
- oracle.com /technetwork/topics/security/cpuapr2006-090826.html
- red-database-security.com /advisory/oracle_cpu_apr_2006.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26053
vdb-entry
-
securitytracker.com
/id?1015961
vdb-entry
Sources
- CVE List CVE-2006-1874
- NVD CVE-2006-1874
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.