Wednesday, December 4, 2013

Google Nexus Vulnerable to DoS attacks via SMS

Google Nexus Vulnerable to DoS attacks via SMS
Google Nexus 5
Google Nexus line of phones can reportedly forced by the attacker to perform a reboot or cannot connect to the mobile internet service, by sending a large number of special SMS message.

The weaknesses found by Bogdan Alecu, a system administrator Levi9 Dutch IT services company and affect all Android 4.x firmware version on the Google Galaxy Nexus 4 and 5. Alecu presented vulnerabilities he discovered Friday when DefCamp security conference in Bucharest, Romania.
SMS Class 0 or Flash SMS is a type of message that defined the GSM specification, messages are displayed directly on the screen and the phone cannot automatically store on the device. After reading the message, the user has the option to keep or reject.

When the message is received Google Nexus phone, it will appear on the active window is surrounded by semi- transparent black overlay that have overlapping effects. The first message if it is not kept or rejected and then received another phone message a second, then the latter will be above the first.

No audio notification when a message is received, even if there is a configuration for regular incoming SMS messages. This means that users will not know have received the message Flash, except when they look at the phone.

When a large number reached about 30 Flash messages received and not terminated the Nexus devices act in an unusual way. According Alecu, general phone will reboot and when a PIN is required to unlock the SIM card, the phone cannot connect to network after reboot. While users might not be aware of it for several hours until they see the phone.

He added that about 20 devices from different vendors were tested, but none were susceptible to this problem.

Alecu claimed to have contacted Google several times since finding these weaknesses, but most receive automatic response. In July one of the Android security team had to respond and said the issue will be fixed in Android 4.3.

0 comments:

Post a Comment

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More