Thursday, January 1, 2009

MD5 Practically Attacked

Although MD5 was theoretically cracked in 2004 by Chinese professor Wang Xiaoyun its practical attack scenario was not shown to the world which was mainly in my opinion due to the complexity of the method and ongoing research to minimize processing and computational power required and therefore detecting collision was not thought a practical approach. MD5 has already been abandoned by the more security savvy organization as their preferred mean of calculating hashes and digitally signing them.

In 2008 researchers from different parts of world gathered again knowing that enough research has been done to practically present the threat to those still using this weak algorithm and worked on finding collision - different messages having same MD5 hash - on MD5 signed SSL certificates and finally succeeded by the end of the year 2008 to create a fake CA certificate issuer and prove the practical implementation of the attack. The irony of the situation is that despite of the fact that MD5 has been proven to contain weakness in its hashing mechanisms many renowned Root CA's still use it.

The researchers disclosed their work at the 25C3 conference in Berlin on the 30th of December by creating a fake ssl certificate signed by RapidSSL which the researchers thought was the weakest of all. VeriSign, the issuers of RapidSSL certificates stopped using MD5 as their checksum algorithm for RapidSSL once the vulnerability was announced

More details can be found on the links mentioned below. 25C3 has also released the videos of the presentation on their website.

Although the private key of this was not released due to the danger of being misused by phishers the method itself was elaborated to a point that this could be done in a lesser amount of time.

Tuesday, December 23, 2008

Microsoft URL Redirection

It seems like microsoft is having a bad year end to 2008 as the host of security vulnerabilities being published not only in its products but also on their website. The following is one more to the pile of security issues faced by the company these days. Although it is a simple url redirect but the purpose it can be used and is being used is really dangerous mainly because of the domain name itself.

The Url redirection bug would basically redirect users clicking on the unsuspected URL as it has the familiar microsoft dot com domain name. For those of us using NOSCRIPT with firefox normally allow microsoft as the trusted source as it hinders with the browsing of the web contents on thier website.

Proof Of Concept

http://www.microsoft.com/ie/ie40/download/?//certstation.com


Let us see how quick Microsoft fixes this vulnerability.

Update: The vulnerability has been patched my Microsoft, the reacted faster then I expected way to go.

Tuesday, July 10, 2007

MSN Messenger 0day

MSN Messenger 8.x has a rather scary bug that is being exploited by people online.  When any of the strings given below are pasted into the private message box on your MSN Messenger, your Messenger will immediately disconnect.  It happens so quickly that you will think that it has not connected in the first place.

If any of your friends asks you to paste the following in your personal message, do not do this, and if for any reason you have done this then have a look at the temporary workaround mentioned below. Temporary because Microsoft have not yet given a patch for this.

Exploit:

n—a_Á—ay±m—aÁÇáç±Çáß±Çá§ÁaÇáDZOÇá—±Çá§±Çár×ÁÇ á+NÇ áLáÇá

OR

(Error) 'A


Workaround:


There are a couple of workarounds for this bug in case you have been a victim.
First is to delete the following folders from your computer and then sign in

C:\Documents and Settings\Username\Application Data\Microsoft\MSN Messenger
C:\Documents and Settings\Username\Local Settings\Application Data\Microsoft\MSN Messenger
C:\Documents and Settings\Username\Local Settings\Application Data\Microsoft\Windows Live Contacts
C:\Documents and Settings\Username\Contacts\

Second is to login using any web messenger and remove the message in the private message area.

This bug exists only in Windows Live Messenger 8.x so using previous versions will also solve the problem.