Re:SSH tunnelling for fun and profit: AutoSSH
by Piskvorrr on Wednesday January 20, 2016 @12:30PM
(#10939723)
Does that boil down to "if root is malicious, Bad Things can happen to other users"? Well...duh. Why not keylog all terminals instead of fumbling with ssh-agent and connection multiplexing?
Re:SSH tunnelling for fun and profit: AutoSSH
by daurnimator on Wednesday January 20, 2016 @10:30PM
(#10943166)
No. The problem with ssh-agent defaults is that someone with root on the server you're SSH'd into can use your SSH private key (which is on your local machine).
ssh-agent is like temporarily uploading your private key to each remote server logged into.
Re:SSH tunnelling for fun and profit: AutoSSH
by Piskvorrr on Thursday January 21, 2016 @05:54AM
(#10944471)
In the same way, a helicopter is like a hot-air baloon. Except it's mostly not - the comparison is very much misleading.
The GP is mixing together SSH agent with agent forwarding, and private keys with key signing by agent.
There is last week's CVE-2016-0777, which is a vulnerability that enables the exploit you are describing, but in a properly patched configuration, without agent forwarding (nb: this feature is off by default), this is not the case. Same with connection multiplexing: off by default (for good reasons). In other words, either a) please explain how that would work, or b) please stop spreading FUD.
Re:SSH tunnelling for fun and profit: AutoSSH
by LinuxBender on Monday February 01, 2016 @10:10PM
(#11017457)
ssh multiplexing is ON by default. The default is `MaxSessions 10`. Unless you have `MaxSessions 1` in your config, then you have it enabled in your environment. If you have 2FA and SOC1/SOC2 controls, then technically you are out of compliance.
Re:SSH tunnelling for fun and profit: AutoSSH
by Piskvorrr on Thursday January 21, 2016 @08:03AM
(#10944901)
An illustrated explanation how ssh-agent is not like copying private key anywhere. http://www.unixwiz.net/techtips/ssh-agent-forwarding.html
Re:SSH tunnelling for fun and profit: AutoSSH
by everythingcli on Thursday January 21, 2016 @03:09AM
(#10944011)
Do you have any material I can read up on to this?
Some time read up on SSH Multiplexing. The default is MaxSessions 10. You auth once, my phishing exercise can utilize your session to connect anywhere you have connected. Nothing will show up in syslog. I can take care of `lastlog` entries since folks cache sudoer privs for so long; or in some cases, don't even require a pw.
I will set up a github with a working example of how to set up a backdoor leveraging ssh multiplexing. I got the idea from a coworker (whitehat) that used a simple ruby script to completely pwn my system. The cool part is, it doesn't require exploiting anything beyond the helpful developer or sysadmin.