iTerm2 CVE-2019-9535 Remote Command Execution Vulnerability



Date Discovered

October 9, 2019


iTerm2 is prone to a remote command-injection vulnerability Attackers can exploit this issue to execute arbitrary commands on the system. iTerm2 version 3.3.5 and prior versions are vulnerable.

Technologies Affected

  • iTerm2 iTerm2 3.0.4
  • iTerm2 iTerm2 3.1.0
  • iTerm2 iTerm2 3.1.5
  • iTerm2 iTerm2 3.2.0
  • iTerm2 iTerm2 3.2.5
  • iTerm2 iTerm2 3.3.0
  • iTerm2 iTerm2 3.3.1
  • iTerm2 iTerm2 3.3.2
  • iTerm2 iTerm2 3.3.3
  • iTerm2 iTerm2 3.3.4
  • iTerm2 iTerm2 3.3.5


Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.

Run all software as a nonprivileged user with minimal access rights.
To limit the impact of a successful exploit, run server software with the least privileges required and in restricted environments while still maintaining functionality.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to websites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Do not follow links provided by unknown or untrusted sources.
Never follow links provided by unknown or untrusted sources.

Implement multiple redundant layers of security.
Implement measures such as '.htaccess' to provide an additional layer of authentication for sensitive or privileged information.

Updates are available. Please see the references or vendor advisory for more information.



Stefan Grönke and Fabian Freyer of Radically Open Security

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.