# CVE-2017-12939: Code injection in n/a

> Remote code execution in Unity Editor allows attackers to run arbitrary code on Windows systems, requiring users to upgrade to patched versions.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmw4-xq8q-x737

## What is CVE-2017-12939?

CVE-2017-12939 is a critical code injection vulnerability in n/a, published on 18 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Remote Code Execution vulnerability was identified in all Windows versions of Unity Editor, e.g., before 5.3.8p2, 5.4.x before 5.4.5p5, 5.5.x before 5.5.4p3, 5.6.x before 5.6.3p1, and 2017.x before 2017.1.0p4.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-12939?

It affects 1 product.


Products: Unity3d Unity Editor.

## How do I fix CVE-2017-12939?

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

## Is CVE-2017-12939 being exploited?

There is no known exploitation of CVE-2017-12939 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-9197](https://insights.sbomify.com/CVE-2019-9197/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12939 and fix it if it is affected.

What it is: CVE-2017-12939 is a critical code injection vulnerability in n/a, published on 18 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12939 in the wild and no public exploit code.

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-2017-12939/ (Markdown: https://insights.sbomify.com/CVE-2017-12939/index.md)
```

## Sources

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

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