# CVE-2014-2967: Command injection in n/a

> Remote attackers can execute arbitrary code via Python API commands in the integrated web server of Autodesk VRED Professional.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g94v-8mrm-p53c

## What is CVE-2014-2967?

CVE-2014-2967 is a critical command injection vulnerability in n/a, published on 7 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Autodesk VRED Professional 2014 before SR1 SP8 allows remote attackers to execute arbitrary code via Python os library calls in Python API commands to the integrated web server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2014-2967?

It affects 1 product.


Products: Autodesk Vred.

## How do I fix CVE-2014-2967?

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

## Is CVE-2014-2967 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-7995](https://insights.sbomify.com/CVE-2024-7995/): Autodesk VRED Design Privilege Escalation Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2967 and fix it if it is affected.

What it is: CVE-2014-2967 is a critical command injection vulnerability in n/a, published on 7 Jul 2014. 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-2014-2967 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-2014-2967/ (Markdown: https://insights.sbomify.com/CVE-2014-2967/index.md)
```

## Sources

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

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