Secure string compare function

Question

I just came across this code in the HTTP Auth library of the Zend Framework. It seems to be using a special string compare function to make it more secure. However, I don't quite understand the comments. Could anybody explain why this function is more secure than doing $a == $b?

/**  * Securely compare two strings for equality while avoided C level memcmp()  * optimisations capable of leaking timing information useful to an attacker  * attempting to iteratively guess the unknown string (e.g. password) being  * compared against.  *  * @param string $a  * @param string $b  * @return bool  */ protected function _secureStringCompare($a, $b) {     if (strlen($a) !== strlen($b)) {         return false;     }     $result = 0;     for ($i = 0; $i < strlen($a); $i++) {         $result |= ord($a[$i]) ^ ord($b[$i]);     }     return $result == 0; } 

Answer 1

It looks like they're trying to prevent timing attacks.

In cryptography, a timing attack is a side channel attack in which the attacker attempts to compromise a cryptosystem by analyzing the time taken to execute cryptographic algorithms. Every logical operation in a computer takes time to execute, and the time can differ based on the input; with precise measurements of the time for each operation, an attacker can work backwards to the input.

Basically, if it takes a different amount of time to compare a correct password and an incorrect password, then you can use the timing to figure out how many characters of the password you've guessed correctly.

Consider an extremely flawed string comparison (this is basically the normal string equality function, with an obvious wait added):

function compare(a, b) {     if(len(a) !== len(b)) {          return false;     }     for(i = 0; i < len(a); ++i) {         if(a[i] !== b[i]) {             return false;         }         wait(10); // wait 10 ms     }     return true; } 

Say you give a password and it (consistently) takes some amount of time for one password, and about 10 ms longer for another. What does this tell you? It means the second password has one more character correct than the first one.

This lets you do movie hacking -- where you guess a password one character at a time (which is much easier than guessing every single possible password).

In the real world, there's other factors involved, so you have to try a password many, many times to handle the randomness of the real world, but you can still try every one character password until one is obviously taking longer, then start on two character password, and so on.

This function still has a minor problem here:

if(strlen($a) !== strlen($b)) {      return false; } 

It lets you use timing attacks to figure out the correct length of the password, which lets you not bother guessing any shorter or longer passwords. In general, you want to hash your passwords first (which will create equal-length strings), so I'm guessing they didn't consider it to be a problem.