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.
Problem types
CWE-829 Inclusion of Functionality from Untrusted Control Sphere
Product status
Any version
References
blog.calif.io/p/mad-bugs-even-cat-readmetxt-is-not
github.com/...ommit/a9e745993c2e2cbb30b884a16617cd5495899f86
news.ycombinator.com/item?id=47809190