# CVE-2001-1494: Path traversal in n/a

> Local users can overwrite arbitrary files via hardlink manipulation in the script command, requiring root execution to trigger the vulnerability.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** Yes
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2001-1494, GHSA-8gpj-8888-5722

## What is CVE-2001-1494?

CVE-2001-1494 is a medium-severity path traversal vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

script command in the util-linux package before 2.11n allows local users to overwrite arbitrary files by setting a hardlink from the typescript log file to any file on the system, then having root execute the script command.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2001-1494?

It affects 7 products.


Products: Avaya Cvlan, Avaya Integrated Management Suit, Avaya Interactive Response, Avaya Intuity Lx, Avaya Message Networking, Avaya Messaging Storage Server, Kernel Util-Linux.

## How do I fix CVE-2001-1494?

Upgrade to a fixed version.

## Is CVE-2001-1494 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0494](https://insights.sbomify.com/CVE-2004-0494/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1494 and fix it if it is affected.

What it is: CVE-2001-1494 is a medium-severity path traversal vulnerability in n/a, published on 21 Jun 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-2001-1494 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-2001-1494/ (Markdown: https://insights.sbomify.com/CVE-2001-1494/index.md)
```

## Sources

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

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