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

> Local users can read sensitive data from world-readable temporary files created by Oracle Forms during large record retrievals.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7fj6-cw4m-wqw7

## What is CVE-2005-2294?

CVE-2005-2294 is a low-severity vulnerability in n/a, published on 17 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Oracle Forms 4.5, 6.0, 6i, and 9i on Unix, when a large number of records are retrieved by an Oracle form, stores a copy of the database tables in a world-readable temporary file, which allows local users to gain sensitive information such as credit card numbers.

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

It affects 1 product.


Products: Oracle Forms.

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

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

## Is CVE-2005-2294 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-83099](https://insights.sbomify.com/CVE-2026-83099/): Auth bypass in Oracle Forms (critical 10.0)
- [CVE-2026-83094](https://insights.sbomify.com/CVE-2026-83094/): Auth bypass in Oracle Forms (critical 9.8)
- [CVE-2026-83095](https://insights.sbomify.com/CVE-2026-83095/): Auth bypass in Oracle Forms (critical 9.8)
- [CVE-2026-83098](https://insights.sbomify.com/CVE-2026-83098/): Auth bypass in Oracle Forms (critical 9.8)
- [CVE-2026-83100](https://insights.sbomify.com/CVE-2026-83100/): Auth bypass in Oracle Forms (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2294 and fix it if it is affected.

What it is: CVE-2005-2294 is a low-severity vulnerability in n/a, published on 17 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2294 in the wild and no public exploit code.

Affected product: n/a. 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-2294/ (Markdown: https://insights.sbomify.com/CVE-2005-2294/index.md)
```

## Sources

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

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