# CVE-2009-2353: File upload in n/a

> Remote attackers can execute arbitrary code by uploading a local executable to the web root via the encoder.php script in eAccelerator.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4xgj-hvh9-w7vh

## What is CVE-2009-2353?

CVE-2009-2353 is a medium-severity vulnerability in n/a, published on 7 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

encoder.php in eAccelerator allows remote attackers to execute arbitrary code by copying a local executable file to a location under the web root via the -o option, and then making a direct request to this file, related to upload of image files.

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

## Which versions are affected by CVE-2009-2353?

It affects 1 product.


Products: Eaccelerator Eaccelerator.

## How do I fix CVE-2009-2353?

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

## Is CVE-2009-2353 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2353 and fix it if it is affected.

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

## Sources

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

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