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

> Remote attackers can execute arbitrary code by uploading a .htaccess file to override MIME types, requiring Apache mod_mime.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 19 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fx7h-w452-rj7j

## What is CVE-2006-3070?

CVE-2006-3070 is a medium-severity vulnerability in n/a, published on 19 Jun 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

write_ok.php in Zeroboard 4.1 pl8, when installed on Apache with mod_mime, allows remote attackers to bypass restrictions for uploading files with executable extensions by uploading a .htaccess file that with an AddType directive that assigns an executable module to files with assumed-safe extensions, as demonstrated by assigning the txt extension to be handled by application/x-httpd-php.

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

It affects 1 product.


Products: Zeroboard Zeroboard.

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

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

## Is CVE-2006-3070 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1820](https://insights.sbomify.com/CVE-2005-1820/): Code injection in n/a (high 7.5)
- [CVE-2005-0380](https://insights.sbomify.com/CVE-2005-0380/): Code injection in n/a (high 7.5)
- [CVE-2004-1419](https://insights.sbomify.com/CVE-2004-1419/): Code injection in n/a (medium 6.8)
- [CVE-2002-1704](https://insights.sbomify.com/CVE-2002-1704/): Code injection in n/a (medium 5.0)
- [CVE-2005-0379](https://insights.sbomify.com/CVE-2005-0379/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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