Skip to main content

Salted hash implementation in Login, in nutshell



The best approach would be hashing the passwords, instead of encrypting them as key management becomes an issue.

Benefits of passwords in form of salted hash:
·         Real passwords are never stored/ displayed/ logged in the system
·         Salts makes dictionary attack very impractical as it’s very difficult to generate    re-computed hash table as salts are random
·         It’s easier to implement as no need of key management

A general approach would be like this (when storing):
·         Generate a long random salt using cryptographically strong functions such as SecureRandom in Java, when user is first time registering himself
·         Use the above salt and hash it with the user’s chosen password using standard and strong hashing algos like SHA 256
·         Now strore the Username, salted hash and respective salt in DB

When retrieving (authenticating user):
·         When the user submits his username-password, retrieve the user’s corresponding salt
·         Concatenate the salt with the user supplied password and apply the same hashing algo (SHA 256) and compute the salted hash
·         Now compare the newly computed salted hash with already stored salted hash against the username
·         If they match, let him in otherwise throw a generic login error, such as ‘Invalid Credentials’

Client side vs. Server side:
·         Always do hashing on server side, irrespective of client side hashing
·         The issue with client side hashing is , even it’s not in clear text, it is as good as a clear text password
·         If you do client side hashing, you need to depend on Javascript, which sometimes is disabled by user, or some browsers may not execute properly
·         Client side hashing is not replacement for TLS/ SSL. Protect all sensitive pages, such as login page over SSL

Constraint:
·         You may not be able to recover user’s original password, if user forgets it as the passwords are not in clear text. You can just users to update with a new password

Comments

Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T