Local Code Execution via SSH Conductor Escape Sequences in iTerm2
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| iTerm2 | iTerm2 | unknown |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Iterm2 | Iterm2 |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.199% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Code Execution via SSH Conductor Escape Sequences in iTerm2 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In iTerm2 through 3.6.9, displaying a .txt file can cause code execution via DCS 2000p and OSC 135 data, if the working directory contains a malicious file whose name is valid output from the conductor encoding path, such as a pathname with an initial ace/c+ substring, aka "hypothetical in-band signaling abuse." This occurs because iTerm2 accepts the SSH conductor protocol from terminal output that does not originate from a legitimate conductor session. | |
| First Time appeared |
Iterm2
Iterm2 iterm2 |
|
| Weaknesses | CWE-829 | |
| CPEs | cpe:2.3:a:iterm2:iterm2:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Iterm2
Iterm2 iterm2 |
|
| References |
| |
| Metrics |
cvssV3_1
|