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

> Remote attackers can force arbitrary image uploads to ImageShack via a malicious file URI in the ActiveX control, requiring user interaction.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gg8w-jxr4-7rcf

## What is CVE-2008-4549?

CVE-2008-4549 is a low-severity vulnerability in n/a, published on 14 Oct 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The ImageShack Toolbar ActiveX control (ImageShackToolbar.dll) in ImageShack Toolbar 4.5.7, possibly including 4.5.7.69, allows remote attackers to force the upload of arbitrary image files to the ImageShack site via a file: URI argument to the BuildSlideShow method.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Imageshack Imageshack Toolbar.

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

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

## Is CVE-2008-4549 being exploited?

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

Public exploit code:

- ImageShack Toolbar 4.5.7 - 'FileUploader' Class InsecureMethod (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4549 is a low-severity vulnerability in n/a, published on 14 Oct 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-4549 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-4549/ (Markdown: https://insights.sbomify.com/CVE-2008-4549/index.md)
```

## Sources

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

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