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

> Remote attackers can delete uploaded files in Google Hack Honeypot File Upload Manager via the delall action, potentially causing data loss.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2008
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g9w4-429x-jw8q

## What is CVE-2008-5283?

CVE-2008-5283 is a medium-severity missing authorization vulnerability in n/a, published on 29 Nov 2008. It can be exploited over the network, with no action from the victim.

### Official description

Google Hack Honeypot (GHH) File Upload Manager 1.3 allows remote attackers to delete uploaded files via unknown vectors related to the delall action to index.php.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. CVE analysis suggests that the most recent version as of 20081128 is 1.2, and the File Upload Manager does not have a "delall" action.

Weakness: CWE-264

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

It affects 1 product.


Products: Ghh Google Hack Honeypot File Upload Manager.

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

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

## Is CVE-2008-5283 being exploited?

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

Public exploit code:

- Google Hack Honeypot File Upload Manager 1.3 - 'delall' Unauthorized File Access (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5283 is a medium-severity missing authorization vulnerability in n/a, published on 29 Nov 2008. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5283 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-5283/ (Markdown: https://insights.sbomify.com/CVE-2008-5283/index.md)
```

## Sources

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

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