CVE-2008-6065 json
Oracle Database Server 10.1, 10.2, and 11g grants directory WRITE permissions for arbitrary pathnames that are aliased in a CREATE OR REPLA…
published 17y ago modified 4mo ago also EUVD-2008-6035
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 1
- Exploit-DB
Summary
Oracle Database Server 10.1, 10.2, and 11g grants directory WRITE permissions for arbitrary pathnames that are aliased in a CREATE OR REPLACE DIRECTORY statement, which allows remote authenticated users with CREATE ANY DIRECTORY privileges to gain SYSDBA privileges by aliasing the pathname of the password directory, and then overwriting the password file through UTL_FILE operations, a related issue to CVE-2006-7141.
Is CVE-2008-6065 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 FencerTimeline
- First public exploit (EDB-32475)
- Published
Exploit prediction
2.20% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-32475 Oracle Database Server 11.1 - 'CREATE ANY Directory' Privilege Escalation remote, 2008-10-13
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
- oracleforensics.com /wordpress/index.php/2008/10/10/create-any-directory-to-sysdba/
-
exchange.xforce.ibmcloud.com
/vulnerabilities/48814
vdb-entry
-
securityfocus.com
/bid/31738
vdb-entry
-
securityfocus.com
/archive/1/497286/100/0/threaded
mailing-list
- oracleforensics.com /wordpress/wp-content/uploads/2008/10/create-any-directory-to-sysdba.pdf
Sources
- CVE List CVE-2008-6065
- NVD CVE-2008-6065
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.