# CVE-2008-6739: Auth bypass in n/a

> Remote attackers can gain administrator privileges by directly accessing the unauthenticated setup script in the ASP Download management script.

- **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:** 21 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4xjg-hhhx-wrf9

## What is CVE-2008-6739?

CVE-2008-6739 is a high-severity authentication bypass vulnerability in n/a, published on 21 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Todd Woolums ASP Download management script 1.03 does not require authentication for setupdownload.asp, which allows remote attackers to gain administrator privileges via a direct request.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2008-6739?

It affects 1 product.


Products: Toddwoolums Asp Download.

## How do I fix CVE-2008-6739?

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

## Is CVE-2008-6739 being exploited?

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

Public exploit code:

- ASP Download 1.03 - Arbitrary Change Administrator Account (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6739 and fix it if it is affected.

What it is: CVE-2008-6739 is a high-severity authentication bypass vulnerability in n/a, published on 21 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6739 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-2008-6739/ (Markdown: https://insights.sbomify.com/CVE-2008-6739/index.md)
```

## Sources

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

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