Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • iterm2 iterm2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 2,800
    • Issues 2,800
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • George Nachman
  • iterm2iterm2
  • Issues
  • #7735
Closed
Open
Issue created Apr 22, 2019 by "><script>alert(1);//@d4wu

Print feature may cause DoS

Thanks for filing an issue! Please answer the questions below so I can help you.

  • iTerm2 version: 3.2.9
  • OS version: MacOS 10.14.3
  • Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window)

Detailed steps to reproduce the problem:

  1. This is content of run.sh and run it
#!/bin/bash

if [ -f /tmp/print ]; then
    rm /tmp/print
fi

for i in {1..100}
do
	echo -e "\x1b\x5b\x69" >> /tmp/print
done
  1. use cat command: cat /tmp/print

What happened: The Windows of Print will open. After click the cancel button 100 times or Kill the iTerm2 process(restart it), User can use iTerm2 again.

What should have happened:

Assignee
Assign to
Time tracking