# CVE-2005-4622: Directory traversal vulnerability in eFileGo 3.01 allows remote attackers to execute arbitrary code, read arbitrary files, and upload arbitrary files via a ...


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Jan 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p4cx-89qv-3gc6

## What is CVE-2005-4622?

CVE-2005-4622 is a high-severity vulnerability in n/a, published on 6 Jan 2006. 

### Official description

Directory traversal vulnerability in eFileGo 3.01 allows remote attackers to execute arbitrary code, read arbitrary files, and upload arbitrary files via a ... (triple dot) in (1) the URL on port 608 and (2) the argument to upload.exe.

## Which versions are affected by CVE-2005-4622?

It affects 1 product.


Products: Efilego Efilego.

## How do I fix CVE-2005-4622?

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

## Is CVE-2005-4622 being exploited?

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

Public exploit code:

- EFileGo 3.0 - Multiple Input Validation Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4623](https://insights.sbomify.com/CVE-2005-4623/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4622 and fix it if it is affected.

What it is: CVE-2005-4622 is a high-severity vulnerability in n/a, published on 6 Jan 2006. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4622 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-2005-4622/ (Markdown: https://insights.sbomify.com/CVE-2005-4622/index.md)
```

## Sources

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

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