CVE-2007-2110 json
Unspecified vulnerability in the Core RDBMS component for Oracle Database 9.0.1.5+, 9.2.0.7, and 10.1.0.4 on Windows systems has unknown im…
published 2007-04-18 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2105
- cvss
- 4.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Core RDBMS component for Oracle Database 9.0.1.5+, 9.2.0.7, and 10.1.0.4 on Windows systems has unknown impact and attack vectors, aka DB03. NOTE: as of 20070424, Oracle has not disputed reliable claims that DB03 occurs because RDBMS uses a NULL Discretionary Access Control List (DACL) for the Oracle process and certain shared memory sections, which allows local users to inject threads and execute arbitrary code via the OpenProcess, OpenThread, and SetThreadContext functions (DB03).
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
securityfocus.com
/archive/1/466329/100/200/threaded
vendor-advisory
-
vupen.com
/english/advisories/2007/1426
vdb-entry, vendor-advisory
-
freelists.org
/archives/oracle-l/12-2006/msg00004.html
mailing-list
-
us-cert.gov
/cas/techalerts/TA07-108A.html
third-party-advisory, us-government-resource
- oracle.com /technetwork/topics/security/cpuapr2007-090632.html
-
securityfocus.com
/bid/23532
vdb-entry
-
securitytracker.com
/id?1017927
vdb-entry
- blackhat.com /presentations/bh-dc-07/Cerrudo/Presentation/bh-dc-07-Cerrudo-ppt.pdf
- red-database-security.com /advisory/oracle_cpu_apr_2007.html
- ngssoftware.com /research/papers/NGSSoftware-OracleCPUAPR2007.pdf
- integrigy.com /security-resources/analysis/Integrigy_Oracle_CPU_April_2007_Analysis.pdf
Sources
- CVE List CVE-2007-2110
- NVD CVE-2007-2110
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.