# CVE-2004-0317: Memory corruption in n/a

> Local users or cluster members can trigger a buffer overflow in LSF eauth, causing denial of service or arbitrary code execution.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6m8c-5c42-fpgx

## What is CVE-2004-0317?

CVE-2004-0317 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in eauth in Load Sharing Facility 4.x, 5.x, and 6.x allows local users or remote attackers within the LSF cluster to cause a denial of service (segmentation fault) and possibly execute arbitrary code via a long LSF_From_PC parameter.

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

It affects 1 product.


Products: Platform Lsf.

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

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

## Is CVE-2004-0317 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0318](https://insights.sbomify.com/CVE-2004-0318/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0317 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. 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-0317 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-0317/ (Markdown: https://insights.sbomify.com/CVE-2004-0317/index.md)
```

## Sources

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

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