Open wvu opened 6 years ago
False positives, as they are not exploits and do not execute commands
False positives, as they do not spawn a telnetd
Likely false positives
CommandShellCleanupCommand
of exit
. register_advanced_options [
# If the session is killed (CTRL+C) rather than exiting cleanly,
# the telnet port remains open, but is unresponsive, and prevents
# re-exploitation until the device is rebooted.
OptString.new('CommandShellCleanupCommand', [true, 'A command to run before the session is closed', 'exit'])
]
TODO
Legend. :-)
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
This was a complaint I raised when we considered
telnetd
as a payload in #9364. It directly resulted in #9353 being written.Several modules spawn an unauthed
telnetd
to create a session against, but when the session is closed or dies, the service remains running, happily providing shells indefinitely. Obviously this is no good if the operator forgets to stop the service.While #9353 was intended to solve this problem, there have been inconsistencies in its execution. We'll want to sort those out in the future. For now, I'm putting up this ticket to document the problem and the modules that need fixing.
This list will need culling. Some of these are false positives, but I wanted to document them all.
Thanks!