News for hackers. Stuff that matters.
Re:Twitter Hacker Says Admin Password Was 'Happiness' by bprater on Tuesday January 06, 2009 @09:55PM (#422879)
This does bring up a good tech question -- how do you prevent people from doing a rapid password attack?

Anyone have an article or some ideas on how this could be done? Is limiting attempts the simplest way?

Even if you do limits, aren't these session-based? I'm guessing a cracker isn't going to respect sessions.

Re:Twitter Hacker Says Admin Password Was 'Happiness' by Tangurena on Tuesday January 06, 2009 @11:10PM (#422981)
Presume that you have some sort of table with userIDs and password hashes (with salt). You should also consider adding some columns like:

1 - LastLoginAttemptedDateTime

2 - LastLoginAttemptedIPAddress

3 - LastSuccessfulLoginDateTime

4 - LastSuccessfulLoginIPAddress

5 - MustChagePasswordAtNextLogin - a boolean flag to indicate they must change their password. You'll set that flag when they're recovering a password, or you've emailed them a temporary password.

6 - UnsuccessfulLoginCount - some number that your logic will use to determine how long they must wait, or if they sit in the penalty box.

7 - AccountLocked - boolean flag, some pointy haired bosses will not permit accounts to be locked out, like mine. And mine refuses to allow passwords to be one-way hashes (his words: we must be able to email the user the password they use). Depending on the security you need, the user of a locked account either has to phone up an unhelp desk, or show up in person.

8 - UserAgreementID - As you change user agreements, you'll want to keep track of what agreement the user agreed to, what day and time. This is something you'll want to log, and if you make substantial changes to the user agreement, you may want to force them to re-agree to the terms of use. You will also want to keep every version of the user agreement stashed away in a table somewhere, in case the lawyers get involved.

9 - UserAgreementDateTime - see #8

Along with a LoginTransaction table that captures attempts - both successful and not to log in, with usernames, date/time, IPaddress. This table should locked down so that a hacker can't delete entries, entries can be added, but not deleted nor changed. You'll do that with triggers ("instead of" triggers for sql server folks).

Perhaps your business logic says that a user can have 3 attempts in a 5 minute window (with no lockouts).

Your code would do something like...user has made 3rd bad attempts, set LastLoginAttemptedDateTime = Now, set UnsuccessfulLoginCount = 3.

Now the user tries to log in 1 minute later...If LastLoginAttemptedDateTime + 5_minutes < Now then log the attempt, LastLoginAttemptedDateTime = Now, reject login attempt EndIf.

If they log in successfully, log that event, set UnsuccessfulLoginCount = 0, set LastSuccessfulLoginDateTime and LastSuccessfulLoginIPAddress to the appropriate values.

Re:Twitter Hacker Says Admin Password Was 'Happiness' by gojomo on Wednesday January 07, 2009 @12:54AM (#423078)
And if the attacker doesn't care which userID they compromise, so they spread their guesses over all userIDs?
Re:Twitter Hacker Says Admin Password Was 'Happiness' by snprbob86 on Wednesday January 07, 2009 @03:39AM (#423197)
This is a very real concern, however it is significantly less likely for such a horizontal attack to succeed. I recommend the grand parent post's solution for startups who aren't yet approaching critical mass and only require protection from the vertical.

Small user sets, such as the Twitter admin accounts, would not be large enough to be successful with a horizontal attack. Provided, of course, that every user has a minimum password complexity, which they did not. Even without complexity requirements, the list of simple words is still prohibitively large in most cases.

That said, if you have even one user among millions with the password "qwerty", he is certainly at risk. However, once you are at a scale prone to this kind of attack, a more sophisticated rate limiting scheme is probably required even for regular web requests.

Re:Twitter Hacker Says Admin Password Was 'Happiness' by festivusr on Wednesday January 07, 2009 @01:28PM (#423737)
I'm sure I'm preaching to the choir, but wow - not using one way hashes is an absolutely terrible security hole.
Re:Twitter Hacker Says Admin Password Was 'Happiness' by nuclear_eclipse on Tuesday January 06, 2009 @10:58PM (#422966)
Look at how programs like Fail2Ban, and many SSH-specific monitoring services work.

Specifically, Fail2Ban follows auth logs for various services, and when it finds clients exceeding per-service configured limits, it adds IPTables rules that ban the offending IP address for a configurable amount of time.

Fail2Ban is packaged in many distributions, including Debian and Ubuntu, and can be compiled on just about any system. I personally use it exclusively to thwart brute force attacks on SSH, SMTP/Postfix, IMAP/Dovecot, and HTTP/Apache.

It should be trivial to add a new set of filter/jail rules for any web application that can log bad authentication attempts to a file, and then you have instant "protection" from most brute force attacks.

Re:Twitter Hacker Says Admin Password Was 'Happiness' by dmoney on Tuesday January 06, 2009 @10:41PM (#422946)
You could double the response time for every successive attempt from the same IP. You'd still need an absolute limit on the account, in case of a distributed attack.
Re:Twitter Hacker Says Admin Password Was 'Happiness' by fuzzmeister on Tuesday January 06, 2009 @10:20PM (#422917)
You could just throw recent login attempts into a table, but that might get big quickly.
Re:Twitter Hacker Says Admin Password Was 'Happiness' by catch23 on Wednesday January 07, 2009 @12:20AM (#423041)
why even bother logging that? just store it in memory someone. have a counting bloom filter remember the set of IPs that tried to login during the last 10 seconds. If your ip is in that set, delay the user by 10 seconds or so...
Re:Twitter Hacker Says Admin Password Was 'Happiness' by amix on Wednesday January 07, 2009 @05:05AM (#423250)
memcached is great for these kind of things.
Re:Twitter Hacker Says Admin Password Was 'Happiness' by shaunxcode on Tuesday January 06, 2009 @10:37PM (#422939)
and thus could also be archived/truncated frequently as it is only relevant within a certain time frame right?
Re:Twitter Hacker Says Admin Password Was 'Happiness' by liuliu on Tuesday January 06, 2009 @10:36PM (#422935)
or memcachedb, or just use mollom.com
Re:Twitter Hacker Says Admin Password Was 'Happiness' by aniketh on Wednesday January 07, 2009 @07:00AM (#423325)
didn't realize an alternative to akismet existed... quick question : how come mollom says 78% of comments are spam, but akismet says 85%?