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

> Remote attackers can execute arbitrary JavaScript code via malicious DAZ Studio files, 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:** 4 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p6wj-gvr2-45fc

## What is CVE-2009-4148?

CVE-2009-4148 is a critical code injection vulnerability in n/a, published on 4 Dec 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

DAZ Studio 2.3.3.161, 2.3.3.163, and 3.0.1.135 allows remote attackers to execute arbitrary JavaScript code via a (1) .ds, (2) .dsa, (3) .dse, or (4) .dsb file, as demonstrated by code that loads the WScript.Shell ActiveX control, related to a "script injection vulnerability."

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

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

It affects 1 product.


Products: Daz3d Daz Studio.

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

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

## Is CVE-2009-4148 being exploited?

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

Public exploit code:

- DAZ Studio - Arbitrary Command Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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