# CVE-2012-4177: Command injection in n/a

> Remote attackers can execute arbitrary programs on Ubisoft Uplay PC clients by exploiting a command line argument vulnerability in the browser plugin.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pq73-g3qh-2rpp

## What is CVE-2012-4177?

CVE-2012-4177 is a critical command injection vulnerability in n/a, published on 7 Aug 2012. 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

The web browser plugin for Ubisoft Uplay PC before 2.0.4 allows remote attackers to execute arbitrary programs via the -orbit_exe_path command line argument.

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

## Which versions are affected by CVE-2012-4177?

It affects 1 product.


Products: Ubi Uplay Pc.

## How do I fix CVE-2012-4177?

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

## Is CVE-2012-4177 being exploited?

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

Public exploit code:

- Ubisoft uplay 2.0.3 ActiveX Control Arbitrary Code Execution (metasploit)
- Ubisoft uplay 2.0.3 - ActiveX Control Arbitrary Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-5453](https://insights.sbomify.com/CVE-2014-5453/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4177 and fix it if it is affected.

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

## Sources

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

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