# CVE-2002-1517: fsr_efs in IRIX 6.5 allows local users to conduct unauthorized file activities via a symlink attack, possibly via the .fsrlast file.


- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cm24-8jw3-w7p7

## What is CVE-2002-1517?

CVE-2002-1517 is a medium-severity vulnerability in Sgi Irix, published on 1 Sep 2004. 

### Official description

fsr_efs in IRIX 6.5 allows local users to conduct unauthorized file activities via a symlink attack, possibly via the .fsrlast file.

## Which versions are affected by CVE-2002-1517?

It affects 2 products.


Products: Sgi Freeware, Sgi Irix.

## How do I fix CVE-2002-1517?

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

## Is CVE-2002-1517 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1517 and fix it if it is affected.

What it is: CVE-2002-1517 is a medium-severity vulnerability in Sgi Irix, published on 1 Sep 2004. 
Exploitation: There is no known exploitation of CVE-2002-1517 in the wild and no public exploit code.

Affected product: Sgi Irix. 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-2002-1517/ (Markdown: https://insights.sbomify.com/CVE-2002-1517/index.md)
```

## Sources

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

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