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

> Remote attackers can overwrite arbitrary files in Sambar Server via a directory traversal attack in the pagecount CGI script.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mwvx-xw2j-2vg6

## What is CVE-2001-1010?

CVE-2001-1010 is a medium-severity path traversal vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in pagecount CGI script in Sambar Server before 5.0 beta 5 allows remote attackers to overwrite arbitrary files via a .. (dot dot) attack on the page parameter.

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

It affects 1 product.


Products: Sambar Sambar Server.

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

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

## Is CVE-2001-1010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1010 exists.

Public exploit code:

- Sambar Server 4.4/5.0 - 'pagecount' File Overwrite (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0509](https://insights.sbomify.com/CVE-2000-0509/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-1286](https://insights.sbomify.com/CVE-2003-1286/): Server-side request forgery in n/a (high 7.5)
- [CVE-2001-1106](https://insights.sbomify.com/CVE-2001-1106/): Weak cryptography in n/a (high 7.5)
- [CVE-2002-0128](https://insights.sbomify.com/CVE-2002-0128/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1292](https://insights.sbomify.com/CVE-2001-1292/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1010 is a medium-severity path traversal vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1010 exists.

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-1010/ (Markdown: https://insights.sbomify.com/CVE-2001-1010/index.md)
```

## Sources

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

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