Vulnerabilities > Iterm2
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-10-23 | CVE-2023-46321 | Unspecified vulnerability in Iterm2 iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. | 9.8 |
2023-10-23 | CVE-2023-46322 | Unspecified vulnerability in Iterm2 iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize ssh hostnames in URLs. | 9.8 |
2023-10-22 | CVE-2023-46300 | Improper Encoding or Escaping of Output vulnerability in Iterm2 iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences related to tmux integration. | 9.8 |
2023-10-22 | CVE-2023-46301 | Improper Encoding or Escaping of Output vulnerability in Iterm2 iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences related to upload. | 9.8 |
2022-11-23 | CVE-2022-45872 | Unspecified vulnerability in Iterm2 iTerm2 before 3.4.18 mishandles a DECRQSS response. | 9.8 |
2019-11-17 | CVE-2019-19022 | Information Exposure vulnerability in Iterm2 iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git repositories. | 7.5 |
2019-10-09 | CVE-2019-9535 | Injection vulnerability in Iterm2 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. | 9.8 |
2017-09-20 | CVE-2015-9231 | Information Exposure vulnerability in Iterm2 iTerm2 3.x before 3.1.1 allows remote attackers to discover passwords by reading DNS queries. | 7.5 |