CVE-2007-0271 json
Unspecified vulnerability in Oracle Database 9.0.1.5 and 9.2.0.7 has unknown impact and attack vectors related to the Log Miner component a…
published 19y ago modified 4mo ago also EUVD-2007-0273
- cvss
- 6.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle Database 9.0.1.5 and 9.2.0.7 has unknown impact and attack vectors related to the Log Miner component and sys.dbms_log_mnr privileges, aka DB04. NOTE: Oracle has not disputed a reliable researcher claim that this is a buffer overflow in the ADD_LOGFILE procedure for the SYS.DBMS_LOGMNR package that allows code execution.
Patch / fix
- secunia.com/advisories/23794 advisory
- us-cert.gov/cas/techalerts/TA07-017A.html advisory
Is CVE-2007-0271 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
4.67% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
secunia.com
/advisories/23794
third-party-advisory, patch, vendor-advisory
-
us-cert.gov
/cas/techalerts/TA07-017A.html
third-party-advisory, patch, us-government-resource
-
securityfocus.com
/archive/1/458475/100/100/threaded
mailing-list
-
securityfocus.com
/bid/22083
vdb-entry
- appsecinc.com /resources/alerts/oracle/2007-01.shtml
- oracle.com /technetwork/topics/security/cpujan2007-101493.html
-
osvdb.org
/32910
vdb-entry
-
securityfocus.com
/archive/1/458006/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/31541
vdb-entry
-
securitytracker.com
/id?1017522
vdb-entry
Sources
- CVE List CVE-2007-0271
- NVD CVE-2007-0271
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.