
Full Disclosure mailing list archives
Re: OpenSSH User Enumeration Time-Based Attack
From: Jann Horn <jann+libev () thejh net>
Date: Thu, 11 Jul 2013 17:41:23 +0200
On Wed, Jul 10, 2013 at 03:38:59PM +0200, Curesec Research Team wrote:
By testing several OpenSSH installations we figured there is a delay of time when it comes to cracking users (not) existing on a system. A normal Brute-force-Attack tests for the correct user and password combination, usually without knowledge if the user on the system exists.
FYI, the openssh guys have known this for quite a while and they don't treat it as an issue worth fixing. They don't want to introduce extra anti-timing code just to prevent user enumeration from working. You can also see a measurable difference when you try logging in with random public RSA keys – around 100% difference over localhost, over the internet it's much lower, but with a few attempts, you can still get good data. Well, for systems that have password auth enabled, your approach seems a lot more reliable. By the way: If you can hog the CPU for seconds by sending a few kilobytes of data, isn't that a DoS issue?
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- OpenSSH User Enumeration Time-Based Attack Curesec Research Team (Jul 10)
- Re: OpenSSH User Enumeration Time-Based Attack Jason Hellenthal (Jul 10)
- Re: OpenSSH User Enumeration Time-Based Attack Swair Mehta (Jul 10)
- Re: OpenSSH User Enumeration Time-Based Attack Jann Horn (Jul 11)
- Re: OpenSSH User Enumeration Time-Based Attack Curesec Research Team (Jul 13)
- Re: OpenSSH User Enumeration Time-Based Attack Florian Reinholz (Jul 13)
- Re: OpenSSH User Enumeration Time-Based Attack Grandma Eubanks (Jul 13)
- <Possible follow-ups>
- Re: OpenSSH User Enumeration Time-Based Attack security curmudgeon (Jul 13)