# CVE-2004-2759: Information disclosure in n/a

> Local users can read portions of deleted files in Sun StorEdge QFS and SAM-QFS file systems by accessing data within sparse files.

- **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:** 11 Mar 2008
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q49p-4xg9-93q2

## What is CVE-2004-2759?

CVE-2004-2759 is a low-severity vulnerability in n/a, published on 11 Mar 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Shared Sun StorEdge QFS and SAM-QFS file systems, as used in Utilization Suite 4.0 through 4.1 and Performance Suite 4.0 through 4.1, might allow local users to read portions of deleted files by accessing data within sparse files.

## Which versions are affected by CVE-2004-2759?

It affects 4 products.


Products: Sun Storedge Qfs, Sun Storedge Sam-Qfs, Sun Storeedge Performance Suite, Sun Storeedge Utilization Suite.

## How do I fix CVE-2004-2759?

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

## Is CVE-2004-2759 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2759 and fix it if it is affected.

What it is: CVE-2004-2759 is a low-severity vulnerability in n/a, published on 11 Mar 2008. 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-2004-2759 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-2004-2759/ (Markdown: https://insights.sbomify.com/CVE-2004-2759/index.md)
```

## Sources

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

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