CVE-2007-2108 json
Unspecified vulnerability in the Core RDBMS component in Oracle Database 9.0.1.5, 9.2.0.8, 10.1.0.5, and 10.2.0.2 on Windows allows remote…
published 2007-04-18 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2103
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.5%
- EPSS 21.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Core RDBMS component in Oracle Database 9.0.1.5, 9.2.0.8, 10.1.0.5, and 10.2.0.2 on Windows allows remote attackers to have an unknown impact, aka DB01. NOTE: as of 20070424, Oracle has not disputed reliable claims that this issue occurs because the NTLM SSPI AcceptSecurityContext function grants privileges based on the username provided even though all users are authenticated as Guest, which allows remote attackers to gain privileges.
Exploit prediction
21.50% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
securityfocus.com
/archive/1/466329/100/200/threaded
vendor-advisory
-
vupen.com
/english/advisories/2007/1426
vdb-entry, vendor-advisory
- ngssoftware.com /papers/database-on-xp.pdf
-
us-cert.gov
/cas/techalerts/TA07-108A.html
third-party-advisory, us-government-resource
- oracle.com /technetwork/topics/security/cpuapr2007-090632.html
-
kb.cert.org
/vuls/id/809457
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/23532
vdb-entry
-
securitytracker.com
/id?1017927
vdb-entry
- 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-2108
- NVD CVE-2007-2108
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.