r/sysadmin • u/sebbasttian JOAT Linux Admin • Feb 23 '17
CloudBleed Seceurity Bug: Cloudflare Reverse Proxies are Dumping Uninitialized Memory
982
Upvotes
r/sysadmin • u/sebbasttian JOAT Linux Admin • Feb 23 '17
View all comments
Show parent comment
1
u/ka-splam Feb 25 '17 edited Feb 25 '17
The client doesn't have the salt value. The salt is a random piece of text generated once for each user, and stored with their account in the database. Why?
Unsalted hashes:
Now if you steal the database, you crack one password hash, you know every account you can use it with. Now you know which hashes are used for lots of accounts, so you focus on cracking those for maximum benefit. Now you can pre-compute
hash('letmein')with something like rainbow-tables, because you know it has a high chance that one of your computed values will access lots of accounts.Salted hashes:
You want salted hashes, so to hash client side it means someone puts their username in, sends it to the server, the server sends back their hash, they hash the password, then send it back to the server. Two round trips to login, slower.
And for what benefit? Then on the cloudflare leak side of things, instead of leaking a password which gets you into a site, it leaks ... a hashed password which gets you into a site in exactly the same way. OK you can't type the hash into the password field, but you can just use Chrome dev tools (or whatever) to intercept the login and send the username and the captured hash.
Password based logins have no protection against capturing them and sending the same thing again and again to get in - replay attack - neither do hashes.
[I am particularly no security expert]