Tuesday, December 27, 2011

Kill switch for iphone and android, here's how it works

I go back for a moment to talk about the news that made scandal recently, the discovery that well on android there's code that enables google to install/remove applications, and its combination that was made with the kill switch this on iphone devices.

I speak because I finally found a very detailed post explaining how it works. But let us start from the beginning, someone on this blog asked me to shed some light on this thing maybe with dedicated article.

Some time ago a certain Jonathan Zdziarski discovered that inside the iphone there is code that would allow Apple to inhibit access to certain applications. How it works is this, periodically the iphone connects to apple's servers and download an application blacklist, if even just one such application is present on the phone it is forbidden the use. After a few weeks of rumors came the confirmation by Steve Jobs on the reality of the thing, justifying it by saying that it was normal to have a "handle to pull" in cases of emergency.

After some time check the same news for android phones, and is again the controversy between the fan boy of toy robot and Apple.

Essentially the mechanisms do the exact same thing, except that no one will ever have clear conditions for which a particular application enters blacklist for iphone (seen highly subjective criteria that are applied to the censorship), while android is used only for software that violates the license and malware in General.

Are there any legal implications in all of this, says Daniele Minotti, first of all the spread of malware (new article text-615 quinquies p.c., Budapest), since the possibility of remote device management by a third party is, in itself, a malware; and if the cancellation is made adding physics also abusive access with damage (ex art. 615-ter c.p.), or computer damage (635-bis of the Criminal Code).

In this Apple, is to recognize, it's more clever in my opinion because its kind of kill-switch incurs only in the first burglary, to spread malware, because his system inhibit the use by the user but does not physically delete as is done on android, which incur even in the last two posts.

We come now to the functioning of the kill switch to Android which is a little more complex. As we saw android communicates with google servers through short messages/command; the kill switch is always based on this principle.

Installation and removal of software on android are not "independent" is not the same phone that installs or removes the apps, this through the market, and more precisely through GTalkService, asks the google server you can install/remove applications, the server responds with a message – that can be of type INSTALL_ASSETT or REMOVE_ASSET – and then the phone completes the operation.

This is because the phone maintains a TCP session/SSL/XMPP constantly open with google servers through GTalkService, persistence is maintained by heartbeat messages that sends your phone periodically, so reinstaurarla everytime the phone connection & switch between 2 g/3 g/hsupa/wifi.

Google this "tunnel" may send these messages to our phone and then give him orders, and so does the kill switch, was sent a remove_asset message and the application disappears from the phone ...

instructions install_asset and remove_asset provided by apk vending.

Now, while the remove_asset statement can only cause nuisance, is the instruction install_asset which creates security risks, we have seen that these messages are clear in a SSL session between google servers and phone but OSH you can Pierce, and then an attacker can perform a MITM (Man In The Middle attack) spoofando these messages and then giving instructions to who knows how many different phonesby installing his potentially malware everywhere (page 14 of the slide by jon oberheide).

1 comment:

  1. Have used AVG security for many years, I recommend this Anti-virus to everybody.

    ReplyDelete