# CVE-2005-0298: Information disclosure in n/a

> Users with read privileges to DIRECTORY objects can obtain sensitive operating system directory location information.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vq3x-w9g8-8pgq

## What is CVE-2005-0298?

CVE-2005-0298 is a medium-severity vulnerability in Oracle Database Server, published on 10 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DIRECTORY objects in Oracle 8i through Oracle 10g contain the location of a specific operating system directory, which allows users with read privileges to a DIRECTORY object to obtain sensitive information.

## Which versions are affected by CVE-2005-0298?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2005-0298?

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

## Is CVE-2005-0298 being exploited?

There is no known exploitation of CVE-2005-0298 in the wild and no public exploit code.

## 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-2005-0298 and fix it if it is affected.

What it is: CVE-2005-0298 is a medium-severity vulnerability in Oracle Database Server, published on 10 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0298 in the wild and no public exploit code.

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-2005-0298/ (Markdown: https://insights.sbomify.com/CVE-2005-0298/index.md)
```

## Sources

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

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