The last time we covered the Heartbleed Virus was a few months back, but it seems like the virus is affecting Android smartphones over Wifi according to A new report from Portuguese security researcher Luis Grangeia.
What is the “HeartBleed Virus” again? it is an encryption flaw (and is being called one of the biggest security threats the Internet has ever seen) that affects SSL (Secure Socket Layer) which is used to transmit data securely over the internet, the vulnerability allows hackers to steal this protected information, the thread works similar on the Heartbleed Virus on Android
Even Samsung KNOX enabled devices are vulnerable, exposing data from the memory which potential contains user credentials, client certificates, or private keys. It is yet unknown how many Android devices have already been affected, but we do know that all AES Wifi routers are vulnerable to the Heartbleed Virus and all Android Jelly Bean 4.1.1 devices.
All though several months have passed since we first heard of the Heartbleed Virus, there are still many websites vulnerable to the attack. Big companies like Google, Facebook etc. have been able to fix the security issue quickly but many smaller business haven’t, just like webmasters can fix the vulnerability, you can also protect your self on your Android device, here is how:
Will the app secure my device against the vulnerability? Currently the app doesnt secure your device against the vulnerability, instead it only tells you if your device is vulnerable. If it isn’t then you shouldn’t have to worry about it since your device is secure.
How do i know if my Android smartphone has been affected? Following the steps mentioned earlier in the post. Specially recommended for users that run Android Jelly Bean 4.1.1, however we still highly recommend anyone running Android to follow our steps since it is still being investigated what other Android versions are vulnerable.
I can scan my smartphone but how do i protect my router? Protecting your smartphone is one thing but your router is a little more complicated. You will have to wait until the manufacturer releases a firmware update that fixes the issue.