# CVE-2005-2693: Path traversal in n/a

> Local attackers can exploit insecure temporary file creation in CVS to overwrite files and execute arbitrary code via symlink attacks.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 25 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2693, DSA-802-1, DSA-806-1, GHSA-rfjx-5fv4-2g47, RHSA-2005:756

## What is CVE-2005-2693?

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

### Official description

cvsbug in CVS 1.12.12 and earlier creates temporary files insecurely, which allows local users to overwrite arbitrary files and execute arbitrary code via a symlink attack.

## Which versions are affected by CVE-2005-2693?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cvs` | Red Hat:enterprise_linux:3::as | All versions | 0:1.11.2-28 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.11.2-28 |
| `cvs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.11.2-28 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.11.2-28 |
| `cvs` | Red Hat:enterprise_linux:3::es | All versions | 0:1.11.2-28 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.11.2-28 |
| `cvs` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.11.2-28 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.11.2-28 |
| `cvs` | Red Hat:enterprise_linux:4::as | All versions | 0:1.11.17-8.RHEL4 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.11.17-8.RHEL4 |
| `cvs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.11.17-8.RHEL4 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.11.17-8.RHEL4 |
| `cvs` | Red Hat:enterprise_linux:4::es | All versions | 0:1.11.17-8.RHEL4 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.11.17-8.RHEL4 |
| `cvs` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.11.17-8.RHEL4 |
| `cvs-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.11.17-8.RHEL4 |

Products: Cvs Cvs.

## How do I fix CVE-2005-2693?

Apply the vendor's patch.

## Is CVE-2005-2693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0804](https://insights.sbomify.com/CVE-2012-0804/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0414](https://insights.sbomify.com/CVE-2004-0414/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0416](https://insights.sbomify.com/CVE-2004-0416/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0418](https://insights.sbomify.com/CVE-2004-0418/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1342](https://insights.sbomify.com/CVE-2004-1342/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2693 and fix it if it is affected.

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

## Sources

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

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