# CVE-2010-2112: Directory traversal vulnerability in the FTP service in FileCOPA before 5.03 allows remote attackers to read or overwrite arbitrary files via unknown vectors.


- **Severity:** High 8.8 (`AV:N/AC:M/Au:N/C:C/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 May 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4gw6-7grx-gcgj

## What is CVE-2010-2112?

CVE-2010-2112 is a high-severity vulnerability in n/a, published on 28 May 2010. 

### Official description

Directory traversal vulnerability in the FTP service in FileCOPA before 5.03 allows remote attackers to read or overwrite arbitrary files via unknown vectors.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2010-2112?

It affects 1 product.


Products: Intervations Filecopa.

## How do I fix CVE-2010-2112?

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

## Is CVE-2010-2112 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1598](https://insights.sbomify.com/CVE-2007-1598/): Memory corruption in n/a (medium 6.8)
- [CVE-2006-3726](https://insights.sbomify.com/CVE-2006-3726/): Memory corruption in n/a (medium 6.5)
- [CVE-2006-3768](https://insights.sbomify.com/CVE-2006-3768/): Integer overflow in n/a (medium 6.4)
- [CVE-2006-0344](https://insights.sbomify.com/CVE-2006-0344/): Path traversal in n/a (medium 6.4)
- [CVE-2006-2254](https://insights.sbomify.com/CVE-2006-2254/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2112 and fix it if it is affected.

What it is: CVE-2010-2112 is a high-severity vulnerability in n/a, published on 28 May 2010. 
Exploitation: There is no known exploitation of CVE-2010-2112 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-2010-2112/ (Markdown: https://insights.sbomify.com/CVE-2010-2112/index.md)
```

## Sources

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

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