# CVE-2006-0332: File upload in n/a

> Remote attackers can upload arbitrary files to a publicly accessible directory in Ecartis, potentially leading to code execution.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 21 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-45g3-mf2x-6mxc

## What is CVE-2006-0332?

CVE-2006-0332 is a medium-severity vulnerability in n/a, published on 21 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pantomime in Ecartis 1.0.0 snapshot 20050909 stores e-mail attachments in a publicly accessible directory, which may allow remote attackers to upload arbitrary files.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Ecartis Ecartis.

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

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

## Is CVE-2006-0332 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0781](https://insights.sbomify.com/CVE-2003-0781/): Information disclosure in n/a (critical 10.0)
- [CVE-2003-0782](https://insights.sbomify.com/CVE-2003-0782/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0467](https://insights.sbomify.com/CVE-2002-0467/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0162](https://insights.sbomify.com/CVE-2003-0162/): Business logic in n/a (high 7.5)
- [CVE-2002-0469](https://insights.sbomify.com/CVE-2002-0469/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0332 is a medium-severity vulnerability in n/a, published on 21 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0332 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-0332/ (Markdown: https://insights.sbomify.com/CVE-2006-0332/index.md)
```

## Sources

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

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