CVE-2005-0701 json
Directory traversal vulnerability in Oracle Database Server 8i and 9i allows remote attackers to read or rename arbitrary files via "\\.\\.…
published 21y ago modified 4mo ago also EUVD-2005-0702
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.1%
- EPSS 18.1% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in Oracle Database Server 8i and 9i allows remote attackers to read or rename arbitrary files via "\\.\\.." (modified dot dot backslash) sequences to UTL_FILE functions such as (1) UTL_FILE.FOPEN or (2) UTL_FILE.frename.
Patch / fix
Is CVE-2005-0701 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-25195)
- Published
Exploit prediction
18.15% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-25195 Oracle Database 8i/9i - Multiple Directory Traversal Vulnerabilities remote, 2005-03-07
- lists.grok.org.uk http://lists.grok.org.uk/pipermail/full-disclosure/2005-March/032273.html referenced PoC, tagged "exploit" by a source, unverified
- argeniss.com http://www.argeniss.com/research/ARGENISS-ADV-030501.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Technology feeds
References
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-March/032273.html
mailing-list, exploit, patch, vendor-advisory
-
argeniss.com
/research/ARGENISS-ADV-030501.txt
exploit, patch, vendor-advisory
-
marc.info
/?l=bugtraq&m=111023635928211&w=2
mailing-list
Sources
- CVE List CVE-2005-0701
- NVD CVE-2005-0701
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.