# CVE-2000-0396: Path traversal in n/a

> Remote attackers can duplicate server files via add.exe to read source code of web scripts like ASP files.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 12 Jul 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-73vq-vfrf-93x8

## What is CVE-2000-0396?

CVE-2000-0396 is a medium-severity path traversal vulnerability in n/a, published on 12 Jul 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The add.exe program in the Carello shopping cart software allows remote attackers to duplicate files on the server, which could allow the attacker to read source code for web scripts such as .ASP files.

## Which versions are affected by CVE-2000-0396?

It affects 1 product.


Products: Pacific Software Carello.

## How do I fix CVE-2000-0396?

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

## Is CVE-2000-0396 being exploited?

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

Public exploit code:

- Pacific Software Carello 1.2.1 - File Duplication / Source Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0683](https://insights.sbomify.com/CVE-2002-0683/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0396 and fix it if it is affected.

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

## Sources

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

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