CVE-2006-1875 in the critical feed json
Unspecified vulnerability in Oracle Database Server 9.0.1.5, 9.2.0.7, and 10.1.0.5 has unknown impact and attack vectors in the Oracle Spat…
published 20y ago modified 4mo ago also EUVD-2006-1875
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle Database Server 9.0.1.5, 9.2.0.7, and 10.1.0.5 has unknown impact and attack vectors in the Oracle Spatial component, aka Vuln# DB11. NOTE: Oracle has not disputed reliable researcher claims that this issue is SQL injection in MDSYS.SDO_LRS_TRIG_INS.
Patch / fix
- securityfocus.com/bid/17590 patch
- securitytracker.com/id?1015961 patch
- secunia.com/advisories/19712 advisory
Is CVE-2006-1875 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
3.50% chance of exploitation in the next 30 days, higher than 89% 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/19712
third-party-advisory, patch, vendor-advisory
-
securityfocus.com
/bid/17590
vdb-entry, patch
-
securitytracker.com
/id?1015961
vdb-entry, patch
-
securityfocus.com
/archive/1/432267/100/0/threaded
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
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26055
vdb-entry
- oracle.com /technetwork/topics/security/cpuapr2006-090826.html
- red-database-security.com /advisory/oracle_cpu_apr_2006.html
Sources
- CVE List CVE-2006-1875
- NVD CVE-2006-1875
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.