# CVE-2022-46387: Command injection in n/a

> Attackers can inject control characters into terminal titles to execute arbitrary commands in ConEmu or Cmder.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 28 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-hfcw-j543-xjp3

## What is CVE-2022-46387?

CVE-2022-46387 is a critical command injection vulnerability in n/a, published on 28 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ConEmu through 220807 and Cmder before 1.3.21 report the title of the terminal, including control characters, which allows an attacker to change the title and then execute it as commands.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2022-46387?

It affects 2 products.


Products: Cmder Cmder, Maximus5 Conemu.

## How do I fix CVE-2022-46387?

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

## Is CVE-2022-46387 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46387 and fix it if it is affected.

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

## Sources

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

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