CVE-2007-2112 json
Unspecified vulnerability in the Authentication component for Oracle Database 10.1.0.5 and 10.2.0.3 has unknown impact and attack vectors,…
published 2007-04-18 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2107
- cvss
- 6.0
- 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 the Authentication component for Oracle Database 10.1.0.5 and 10.2.0.3 has unknown impact and attack vectors, aka DB05. NOTE: as of 20070424, Oracle has not disputed reliable claims that this issue allows remote authenticated users to bypass the AUTH_ALTER_SESSION security policies via a logon trigger ("AFTER LOGON ON DATABASE" trigger directive), a related issue to CVE-2006-0547.
Exploit prediction
4.03% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/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
-
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
- red-database-security.com /advisory/bypass_oracle_logon_trigger.html
-
securitytracker.com
/id?1017927
vdb-entry
- red-database-security.com /advisory/oracle_cpu_apr_2007.html
-
securityfocus.com
/archive/1/466151/100/0/threaded
mailing-list
- ngssoftware.com /research/papers/NGSSoftware-OracleCPUAPR2007.pdf
- integrigy.com /security-resources/analysis/Integrigy_Oracle_CPU_April_2007_Analysis.pdf
Sources
- CVE List CVE-2007-2112
- NVD CVE-2007-2112
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.