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

> Remote attackers can execute arbitrary code by uploading malicious files due to insufficient server-side validation in DUware DUbanner.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 17 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q253-pp4f-vcfr

## What is CVE-2006-2428?

CVE-2006-2428 is a high-severity vulnerability in n/a, published on 17 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

add.asp in DUware DUbanner 3.1 allows remote attackers to execute arbitrary code by uploading files with arbitrary extensions, such as ASP files, probably due to client-side enforcement that can be bypassed.  NOTE: some of these details are obtained from third party information, since the raw source is vague.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Duware Dubanner Project Duware Dubanner.

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

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

## Is CVE-2006-2428 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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