# CVE-2003-0977: Path traversal in n/a

> Attackers can create arbitrary directories and files in the root filesystem via malformed module requests to the CVS server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0977, GHSA-4jrq-7cgx-qq88

## What is CVE-2003-0977?

CVE-2003-0977 is a high-severity path traversal vulnerability in Slackware Slackware Linux, published on 10 Dec 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CVS server before 1.11.10 may allow attackers to cause the CVS server to create directories and files in the file system root directory via malformed module requests.

## Which versions are affected by CVE-2003-0977?

It affects 2 products.


Products: Cvs Cvs, Slackware Slackware Linux.

## How do I fix CVE-2003-0977?

Upgrade to a fixed version.

## Is CVE-2003-0977 being exploited?

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

## Other vulnerabilities in Slackware Slackware Linux

- [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-2003-0977 and fix it if it is affected.

What it is: CVE-2003-0977 is a high-severity path traversal vulnerability in Slackware Slackware Linux, published on 10 Dec 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0977 in the wild and no public exploit code.

Affected product: Slackware Slackware Linux. 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-2003-0977/ (Markdown: https://insights.sbomify.com/CVE-2003-0977/index.md)
```

## Sources

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

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