# CVE-2006-1383: Path traversal in n/a

> Authenticated attackers can determine the existence of files outside the document root in Baby FTP Server via directory traversal techniques.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xh3q-r5fw-h5x8

## What is CVE-2006-1383?

CVE-2006-1383 is a medium-severity path traversal vulnerability in n/a, published on 24 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Baby FTP Server (BabyFTP) 1.24 allows remote authenticated users to determine existence of files outside the intended document root via unspecified manipulations, which generate different error messages depending on whether a file exists or not.

## Which versions are affected by CVE-2006-1383?

It affects 1 product.


Products: Pablo Software Solutions Baby Ftp Server.

## How do I fix CVE-2006-1383?

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

## Is CVE-2006-1383 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2209](https://insights.sbomify.com/CVE-2002-2209/): Other in n/a (critical 10.0)
- [CVE-2003-1300](https://insights.sbomify.com/CVE-2003-1300/): Denial of service in n/a (medium 5.0)
- [CVE-2003-1299](https://insights.sbomify.com/CVE-2003-1299/): Path traversal in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1383 and fix it if it is affected.

What it is: CVE-2006-1383 is a medium-severity path traversal vulnerability in n/a, published on 24 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1383 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-2006-1383/ (Markdown: https://insights.sbomify.com/CVE-2006-1383/index.md)
```

## Sources

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

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