# CVE-2019-9535: iTerm2, up to and including version 3.3.5, with tmux integration is vulnerable to remote command execution

> Attackers can execute arbitrary commands on victim machines via malicious terminal output when iTerm2 uses tmux integration.

- **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:** 9 Oct 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jwm6-6mgm-w3f5

## What is CVE-2019-9535?

CVE-2019-9535 is a critical command injection vulnerability in iTerm2, published on 9 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in the way that iTerm2 integrates with tmux's control mode, which may allow an attacker to execute arbitrary commands by providing malicious output to the terminal. This affects versions of iTerm2 up to and including 3.3.5. This vulnerability may allow an attacker to execute arbitrary commands on their victim's computer by providing malicious output to the terminal. It could be exploited using command-line utilities that print attacker-controlled content.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

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

It affects 1 product.


Products: Iterm2 Iterm2.

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

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

## Is CVE-2019-9535 being exploited?

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

## Other vulnerabilities in iTerm2

- [CVE-2024-38395](https://insights.sbomify.com/CVE-2024-38395/): Code injection in n/a (critical 9.8)
- [CVE-2024-38396](https://insights.sbomify.com/CVE-2024-38396/): Code injection in n/a (critical 9.8)
- [CVE-2023-46300](https://insights.sbomify.com/CVE-2023-46300/): Code injection in n/a (critical 9.8)
- [CVE-2023-46301](https://insights.sbomify.com/CVE-2023-46301/): Code injection in n/a (critical 9.8)
- [CVE-2023-46321](https://insights.sbomify.com/CVE-2023-46321/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9535 is a critical command injection vulnerability in iTerm2, published on 9 Oct 2019. 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-2019-9535 in the wild and no public exploit code.

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

## Sources

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

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