# CVE-2008-2832: File upload in n/a

> Remote attackers with admin privileges can upload and execute arbitrary code via unrestricted file upload in aspWebCalendar.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-43xj-hvp7-hp7w

## What is CVE-2008-2832?

CVE-2008-2832 is a critical vulnerability in n/a, published on 24 Jun 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in calendar_admin.asp in Full Revolution aspWebCalendar 2008 allows remote attackers to upload and execute arbitrary code via the FILE1 parameter in an uploadfileprocess action, probably followed by a direct request to the file in calendar/eventimages/.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Fullrevolution Aspwebcalendar2008.

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

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

## Is CVE-2008-2832 being exploited?

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

Public exploit code:

- AspWebCalendar 2008 - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2832 is a critical vulnerability in n/a, published on 24 Jun 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2832 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-2832/ (Markdown: https://insights.sbomify.com/CVE-2008-2832/index.md)
```

## Sources

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

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