POODLE vulnerability

Do you think that your online bank transactions are safe?Well, how do you say so?We normally say these data are safe by seeing a padlock(secure) icon on the browser near the URL.The padlock symbol represents https.Https is secure than HTTP by a single difference that it is encrypted.Do you think if your data is encrypted, will it be safe?

I too thought that the https is secure until these SSL vulnerabilities were discovered.These include POODLE and heartbleed vulnerability.Secure sockets layer protocol was developed to secure online data.The main requirement for SSL protocol is the SSL certificate.

HOW SSL WORKS?

  • The browser sends an https request to the web server.
  • the web server sends a copy of its SSL certificate to the browser.
  • The browser checks the validity(key length, expiry, trusted CA etc) of the SSL certificate.
  • If it is valid, the browser generates a session key(encrypted with a public key) and sends it to the server.
  • Once receiving the session key, the server decrypts it using its private key and sends an acknowledgment to the browser.
  • Thus an encrypted session is established

POODLE(padding oracle on downgraded legacy encryption)

This is vulnerability is common to SSL version3.The main trend of exploiting is the man-in-the-middle attacks.

In SSL, the data is divided into small chunks and is encrypted.Each part of the data is encrypted using the size of the previous part.

Depending on the hashing algorithm(SHA, MD5 etc) there is a fixed length of the data.If the part of the data does not match the length, then it is padded.The last part of the data contains the number of padding bits.This is the flaw which can be utilized.

As a man-in-the-middle, the attacker tampers a part of the data.This affects the next encryption since each encryption depends also on the previous data.

 

This causes a change in encrypted traffic and the server on the other end will observe this abnormality and terminates its connection.But if the attacker tampers the user using the correct number(possibility is 1:256), the server will not terminate the connection and the attacker could decrypt the data.By using javascript this attack can be automated to do 1000times in a minute.Thus, the attacker can easily get away with the critical information.

PRACTICAL SCENARIO:

The attacker will host a webpage(containing malicious javascript) similar to the original webpage.When end user access that webpage.The attacker can exploit this situation by stealing the authentication cookies which contains the password.But for this to happen, the attacker must downgrade the SSL version of both browser and server to 3.This can be done during the SSL handshake as a man-in-the-middle.

Recommendation

The main recommendation is to disable SSL

Upgrade to latest version of TLS

 

Facebook Comments