# CVE-2008-2003: Missing authorization in n/a

> Remote attackers can cause denial of service or execute arbitrary code by accessing unprotected executables in the web root.

- **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:** 28 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pfc4-99pq-48xf

## What is CVE-2008-2003?

CVE-2008-2003 is a high-severity missing authorization vulnerability in n/a, published on 28 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BadBlue 2.72 Personal Edition stores multiple programs in the web document root with insufficient access control, which allows remote attackers to (1) cause a denial of service via multiple invocations of uninst.exe, and have an unknown impact via (2) badblue.exe and (3) dyndns.exe.  NOTE: this can be leveraged for arbitrary remote code execution in conjunction with CVE-2007-6378.

Weakness: CWE-264

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

It affects 1 product.


Products: Badblue Badblue.

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

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

## Is CVE-2008-2003 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6377](https://insights.sbomify.com/CVE-2007-6377/): Memory corruption in n/a (high 7.5)
- [CVE-2007-6378](https://insights.sbomify.com/CVE-2007-6378/): Path traversal in n/a (high 7.5)
- [CVE-2007-6379](https://insights.sbomify.com/CVE-2007-6379/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2003 is a high-severity missing authorization vulnerability in n/a, published on 28 Apr 2008. 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-2008-2003 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-2008-2003/ (Markdown: https://insights.sbomify.com/CVE-2008-2003/index.md)
```

## Sources

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

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