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

> Remote attackers can execute arbitrary JavaScript code via malicious scene packages in Autodesk Softimage, requiring user interaction to open the file.

- **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:** 24 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qv88-c9vm-fw8p

## What is CVE-2009-3576?

CVE-2009-3576 is a critical code injection vulnerability in n/a, published on 24 Nov 2009. 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

Autodesk Softimage 7.x and Softimage XSI 6.x allow remote attackers to execute arbitrary JavaScript code via a scene package containing a Scene Table of Contents (aka .scntoc) file with a Script_Content element, as demonstrated by code that loads the WScript.Shell ActiveX control.

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

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

It affects 2 products.


Products: Autodesk Autodesk Softimage, Autodesk Autodesk Softimage Xsi.

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

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

## Is CVE-2009-3576 being exploited?

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

Public exploit code:

- Autodesk SoftImage Scene TOC - Arbitrary Command Execution (exploitdb)
- Autodesk SoftImage 7.0 Scene - '.TOC' File Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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