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

> Remote attackers can execute arbitrary code by tricking users into opening malicious Maya files containing embedded MEL commands.

- **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-4hwc-m82x-xf7x

## What is CVE-2009-3578?

CVE-2009-3578 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 Maya 8.0, 8.5, 2008, 2009, and 2010 and Alias Wavefront Maya 6.5 and 7.0 allow remote attackers to execute arbitrary code via a (1) .ma or (2) .mb file that uses the Maya Embedded Language (MEL) python command or unspecified other MEL commands, related to "Script Nodes."

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

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

It affects 2 products.


Products: Autodesk Alias Wavefront Maya, Autodesk Autodesk Maya.

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

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

## Is CVE-2009-3578 being exploited?

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

Public exploit code:

- Autodesk Maya Script - Nodes Arbitrary Command Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3578 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-3578 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-3578/ (Markdown: https://insights.sbomify.com/CVE-2009-3578/index.md)
```

## Sources

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

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