# CVE-2009-4850: Code injection in n/a

> Remote attackers can execute arbitrary programs by tricking users into loading a malicious .exe URL via the SceneURL property in the Awingsoft Winds3D Viewer plugin.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 7 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jf47-mr6f-3vgr

## What is CVE-2009-4850?

CVE-2009-4850 is a critical code injection vulnerability in n/a, published on 7 May 2010. 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 Awingsoft Awakening Winds3D Viewer plugin 3.5.0.9 allows remote attackers to execute arbitrary programs via a SceneURL property value with a URL for a .exe file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2009-4850?

It affects 1 product.


Products: Awingsoft Awakening Winds3d Viewer Plugin.

## How do I fix CVE-2009-4850?

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

## Is CVE-2009-4850 being exploited?

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

Public exploit code:

- AwingSoft Winds3D Player 3.5 SceneURL Download and Execute (metasploit)
- AwingSoft Winds3D Player 3.5 - SceneURL Download and Execute (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2386](https://insights.sbomify.com/CVE-2009-2386/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4850 and fix it if it is affected.

What it is: CVE-2009-4850 is a critical code injection vulnerability in n/a, published on 7 May 2010. 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-2009-4850 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-2009-4850/ (Markdown: https://insights.sbomify.com/CVE-2009-4850/index.md)
```

## Sources

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

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