Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timing attack: Easy to figure out whether a user exists or not #37

Open
untitaker opened this issue Feb 15, 2016 · 1 comment
Open

Timing attack: Easy to figure out whether a user exists or not #37

untitaker opened this issue Feb 15, 2016 · 1 comment
Labels

Comments

@untitaker
Copy link
Owner

  • Login with valid username and invalid password: Long response time
  • Login with invalid username: Short response time

https://cryptocoding.net/index.php/Coding_rules#Avoid_branchings_controlled_by_secret_data

The question is, do we care?

@untitaker
Copy link
Owner Author

I've deleted previous comment, the test was sending malformed form data that was immediately rejected during parsing. The timing difference is very obvious when using:

ab -n 1000 -p form -m POST -T 'application/x-www-form-urlencoded' -H 'Referer: http://localhost:6767/login/' http://localhost:6767/login/

With the form file containing either:

  • user=asdf&pass=asdf (nonexisting user)
  • user=demo&pass=asdf (existing user)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant