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

> Remote attackers can force arbitrary file uploads via the PicturePusher ActiveX control in Microsoft Digital Image, requiring user interaction and specific browser settings.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-99f6-r2q3-8f37

## What is CVE-2008-4493?

CVE-2008-4493 is a medium-severity vulnerability in n/a, published on 8 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

Microsoft PicturePusher ActiveX control (PipPPush.DLL 7.00.0709), as used in Microsoft Digital Image 2006 Starter Edition, allows remote attackers to force the upload of arbitrary files by using the AddString and Post methods and a modified PostURL to construct an HTTP POST request.  NOTE: this issue might only be exploitable in limited environments or non-default browser settings.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Microsoft Digital Image.

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

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

## Is CVE-2008-4493 being exploited?

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

Public exploit code:

- Microsoft PicturePusher - ActiveX Cross-Site Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4493 is a medium-severity vulnerability in n/a, published on 8 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-4493 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-4493/ (Markdown: https://insights.sbomify.com/CVE-2008-4493/index.md)
```

## Sources

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

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