# CVE-1999-0049: Path traversal in n/a

> The Csetup utility in IRIX allows attackers to create or overwrite arbitrary files, potentially compromising system integrity.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-p4jq-fjvc-qmw3

## What is CVE-1999-0049?

CVE-1999-0049 is a high-severity path traversal vulnerability in Sgi Irix, published on 29 Sep 1999. 

### Official description

Csetup under IRIX allows arbitrary file creation or overwriting.

## Which versions are affected by CVE-1999-0049?

It affects 1 product.


Products: Sgi Irix.

## How do I fix CVE-1999-0049?

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

## Is CVE-1999-0049 being exploited?

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

## Other vulnerabilities in Sgi Irix

- [CVE-2002-1584](https://insights.sbomify.com/CVE-2002-1584/): Privilege escalation in n/a (critical 10.0)
- [CVE-2004-0139](https://insights.sbomify.com/CVE-2004-0139/): Other in n/a (critical 10.0)
- [CVE-2003-0575](https://insights.sbomify.com/CVE-2003-0575/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0473](https://insights.sbomify.com/CVE-2003-0473/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-0359](https://insights.sbomify.com/CVE-2002-0359/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0049 and fix it if it is affected.

What it is: CVE-1999-0049 is a high-severity path traversal vulnerability in Sgi Irix, published on 29 Sep 1999. 
Exploitation: There is no known exploitation of CVE-1999-0049 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-1999-0049/ (Markdown: https://insights.sbomify.com/CVE-1999-0049/index.md)
```

## Sources

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

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