# CVE-2019-12805: NC Launcher 2 Arbitrary Command Injection Vulnerability

> Remote attackers can execute arbitrary commands via a malicious web page exploiting a custom protocol handler in the NCSOFT Game Launcher.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Aug 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fmvh-gcvc-qpm3

## What is CVE-2019-12805?

CVE-2019-12805 is a high-severity command injection vulnerability in NCSOFT NC Launcher2, published on 9 Aug 2019. 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

NCSOFT Game Launcher, NC Launcher2 2.4.1.691 and earlier versions have a vulnerability in the custom protocol handler that could allow remote attacker to execute arbitrary command. User interaction is required to exploit this vulnerability in that the target must visit a malicious web page. This can be leveraged for code execution in the context of the current user.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2019-12805?

It affects 1 product.


Products: Ncsoft Nc Launcher2.

## How do I fix CVE-2019-12805?

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

## Is CVE-2019-12805 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12805 and fix it if it is affected.

What it is: CVE-2019-12805 is a high-severity command injection vulnerability in NCSOFT NC Launcher2, published on 9 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12805 in the wild and no public exploit code.

Affected product: NCSOFT NC Launcher2. 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-2019-12805/ (Markdown: https://insights.sbomify.com/CVE-2019-12805/index.md)
```

## Sources

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

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