{"uuid": "54f80bd0-2d9a-48b5-9f5c-e2fe2e866dd5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2017-7629", "type": "seen", "source": "https://t.me/hacking_Attack/118642", "content": "hacking: security in practice\nBest way to handle multiple persistent reverse shells?\n\nHey everybody, so I\u2019ve got a few servers that I\u2019ve set up with the lovely vulnerable IIS 6.0 OS, I gain shells to then using a vulnerability (CVE-2017-7629, Buffer overflow in the ScStoragePathFromUrl function in the WebDAV service). I usually gain the shell by running a script that uploads a msfvenom payload that calls back to a server running a handler via msfconsole. Or I just use msfconsole for all of it. Either way I usually gain privilege escalation and install persistence to where I can reboot the target and no matter what it\u2019ll start a reverse shell back to me so long as I have my handler running to catch it. \n\nMy question is, if I have more than one of these severs homing back to me, what would be the best way to handle them? For now, I\u2019m just setting each one to call back on a different port. E.g.:\nServer A1 - call back to C2 server using <ipon Port 4444\n\n \n\nServer A2 - call back to C2 server using <ipon port 5555\n\n \netc. \n\nSo to get back into whichever one I want, I\u2019ll just change the LPORT on my handler in msfconsole. Is this the best way to handle multiple persistent shells?\n\nsubmitted by /u/ReactNativeIsTooHard \n[link] [comments]", "creation_timestamp": "2026-09-02T01:01:09.148059Z"}