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

> Local attackers can modify other users' files via symlink attacks on temporary files in the rcs2log utility.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g4f4-9r8p-qw3r

## What is CVE-2001-1301?

CVE-2001-1301 is a low-severity path traversal vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

rcs2log, as used in Emacs 20.4, xemacs 21.1.10 and other versions before 21.4, and possibly other packages, allows local users to modify files of other users via a symlink attack on a temporary file.

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

It affects 2 products.


Products: Gnu Emacs, Xemacs Xemacs.

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

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

## Is CVE-2001-1301 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6109](https://insights.sbomify.com/CVE-2007-6109/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-39331](https://insights.sbomify.com/CVE-2024-39331/): Code injection in n/a (critical 9.8)
- [CVE-2024-53920](https://insights.sbomify.com/CVE-2024-53920/): Code injection in n/a (high 7.8)
- [CVE-2024-30202](https://insights.sbomify.com/CVE-2024-30202/): Code injection in n/a (high 7.8)
- [CVE-2023-2491](https://insights.sbomify.com/CVE-2023-2491/): Command injection in emacs (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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