# CVE-2006-7141: Path traversal in n/a

> Authenticated users can read and modify arbitrary files via path traversal in utl_file functions if insecure directory privileges are configured.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-26r9-9grm-j62r

## What is CVE-2006-7141?

CVE-2006-7141 is a medium-severity path traversal vulnerability in Oracle Database Server, published on 7 Mar 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Absolute path traversal vulnerability in Oracle Database Server, when utl_file_dir is set to a wildcard value or "CREATE ANY DIRECTORY to PUBLIC" privileges exist, allows remote authenticated users to read and modify arbitrary files via full filepaths to utl_file functions such as (1) utl_file.put_line and (2) utl_file.get_line, a related issue to CVE-2005-0701.  NOTE: this issue is disputed by third parties who state that this is due to an insecure configuration instead of an inherent vulnerability

## Which versions are affected by CVE-2006-7141?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2006-7141?

No fix has been published for CVE-2006-7141 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-7141 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7141 exists.

Public exploit code:

- Oracle 9i/10g - 'utl_file' FileSystem Access (exploitdb)

## Other vulnerabilities in Oracle Database Server

- [CVE-2015-4863](https://insights.sbomify.com/CVE-2015-4863/): Other in n/a (critical 10.0)
- [CVE-2013-1534](https://insights.sbomify.com/CVE-2013-1534/): Other in n/a (critical 10.0)
- [CVE-2010-0071](https://insights.sbomify.com/CVE-2010-0071/): Other in n/a (critical 10.0)
- [CVE-2009-1979](https://insights.sbomify.com/CVE-2009-1979/): Other in n/a (critical 10.0)
- [CVE-2009-1985](https://insights.sbomify.com/CVE-2009-1985/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7141 and fix it if it is affected.

What it is: CVE-2006-7141 is a medium-severity path traversal vulnerability in Oracle Database Server, published on 7 Mar 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7141 exists.

Affected product: Oracle Database Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-7141/ (Markdown: https://insights.sbomify.com/CVE-2006-7141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-7141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-7141
- OSV: https://osv.dev/vulnerability/CVE-2006-7141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-7141/
Summaries are generated and may contain mistakes; the official description above is the record.