Forgot your password?
typodupeerror
Cellphones Data Storage Privacy Security

Wiping a Smartphone Still Leaves Data Behind 155

Posted by Soulskill
from the why-you-always-smash-them-with-a-hammer-before-reselling-them dept.
KindMind writes "To probably no one's surprise, wiping a smartphone by standard methods doesn't get all the data erased. From an article at Wired: 'Problem is, even if you do everything right, there can still be lots of personal data left behind. Simply restoring a phone to its factory settings won't completely clear it of data. Even if you use the built-in tools to wipe it, when you go to sell your phone on Craigslist you may be selling all sorts of things along with it that are far more valuable — your name, birth date, Social Security number and home address, for example. ... [On a wiped iPhone 3G, mobile forensics specialist Lee Reiber] found a large amount of deleted personal data that he recovered because it had not been overwritten. He was able to find hundreds of phone numbers from a contacts database. Worse, he found a list of nearly every Wi-Fi and cellular access point the phone had ever come across — 68,390 Wi-Fi points and 61,202 cell sites. (This was the same location data tracking that landed Apple in a privacy flap a few years ago, and caused it to change its collection methods.) Even if the phone had never connected to any of the Wi-Fi access points, iOS was still logging them, and Reiber was able to grab them and piece together a trail of where the phone had been turned on.'"
This discussion has been archived. No new comments can be posted.

Wiping a Smartphone Still Leaves Data Behind

Comments Filter:
  • by guruevi (827432) <evi AT smokingcube DOT be> on Tuesday April 02, 2013 @03:52PM (#43341977) Homepage

    Most decent cell phones have built-in encryption which wipes the phone by simply deleting the built-in keys. Some cheap-ass droids and the 'feature-phones' may not have it built-in but it's fairly easy to wipe a phone that has the feature.

    Off course, if you use the wrong methods (such as simply 'restoring' the phone) or using unencrypted external media, not much is going to help you. If you really need to get rid of your data (eg. in an enterprise environment) I would hope those in charge of the devices would know how to configure and manage the phones correctly so they can be remotely wiped etc

  • by kallisti (20737) <rmidthun@yahoo.com> on Tuesday April 02, 2013 @03:54PM (#43341997) Homepage

    The key line: "On a wiped iPhone 3G"

    Starting with the iPhone3GS, iOS encrypts everything with a random AES256 key. When you say to wipe the device, it erases that key rendering everything else unusable. This is mentioned in the article, but downplayed. It's been a long time since you could even buy an iPhone 3G, so it seems alarmist to bring it up now.

    http://blog.itsecurityexpert.co.uk/2011/10/securely-wiping-your-personal-data-from.html [itsecurityexpert.co.uk]

  • by perpenso (1613749) on Tuesday April 02, 2013 @03:57PM (#43342015)

    Did the previous owner use the "erase all content and settings" feature of that phone? Or just restore it. That would have been using the built in tool and would have overwrote the data. http://support.apple.com/kb/ht2110 [apple.com]

    The author used the last iPhone (3G) running the last iOS version (4) that would exhibit such behavior. It seems a contrived test.

    An upgrade to iOS 5 would fix the problem on the 3G. On newer phones the encryption key needed to access the data is destroyed, so the problem never would have occurred.

  • Re:Can't hide it (Score:5, Informative)

    by BasilBrush (643681) on Tuesday April 02, 2013 @03:58PM (#43342045)

    With iOS it certainly isn't. Note the iPhones used in the article were deliberately selected to be very old. iPhone 3G.

    With newer iPhones, every single byte is written using a hardware based encryption key. AES-256. Wiping the phone involves deleting just the key. At that stage none of the phone's data is recoverable. Not by anyone.

  • by jxander (2605655) on Tuesday April 02, 2013 @04:01PM (#43342075)

    Some napkin math, assuming he purchased the phone in July 2008 when 3G went on sale, and it's been in use constantly for the last 57 months ... and ball-parking 30 days/month ... he hit 40 Wi-Fi points and 36 cell towers every day.

    Even with the assumption that these are not unique access points (i.e. his home WiFi is counted 3 or 4 times a day, depending on how often he comes and goes) ... that's still an insane number. If we change the time-frame to 2 years, roughly the average lifespan between upgrades, he's up to 95 WiFi points per day.

    Quite the busy bee.

  • by Andy Dodd (701) <atd7@cCOWornell.edu minus herbivore> on Tuesday April 02, 2013 @04:02PM (#43342085) Homepage

    The article makes no mention of WHICH Android revision each of the given phones tested was using.

    It was a known problem with Gingerbread and earlier that the wipe method used by most Android devices was insufficient. That's why Google added secure erase prior to reformat with ICS (maybe HC too, not sure...)

    https://android.googlesource.com/platform/system/extras/+/c2470654d4b4db09a7052fc5fa108ac21f1b1948 [googlesource.com]

    Interesting result of this: Samsung's eMMC chips that were shipped in the Galaxy S II and original Galaxy Note couldn't handle this secure erase command properly, and using a standard "secure" wipe had a pretty good chance of corrupting the wear leveller so badly the chip would be rendered useless. (Samsung's own recoveries were "neutered" so as not to issue a secure erase command.)

    TL;DR - Unless crippled by the manufacturer, any recent Android device (ICS or newer) should not have any of the issues with data remaining easily recoverable after a wipe described by this article. LG didn't do anything special here - they just implemented ICS or later and that's all that was needed.

  • by Alter_3d (948458) on Tuesday April 02, 2013 @04:07PM (#43342149)

    The author used the last iPhone (3G) running the last iOS version (4) that would exhibit such behavior. It seems a contrived test. An upgrade to iOS 5 would fix the problem on the 3G. On newer phones the encryption key needed to access the data is destroyed, so the problem never would have occurred.

    Sorry, but the iPhone 3G tops out at version 4.1.2. The 3GS, on the other hand, does have support for iOS 6, if I remember correctly.

  • by Anonymous Coward on Tuesday April 02, 2013 @04:17PM (#43342223)

    The bad news is that only since Android 4.0 that there has been decent encryption in devices. Before that, only some Motorola devices had some ability to encrypt the SD card and the main filesystems.

    The good news is that Android has grown up, and uses dmcrypt to encrypt the /data partition. One can even have the passphrase that decrypts the filesystem separate from the screen unlocking PIN, using a command line and the vdc cryptfs changepw command. This way, if the device falls into the wrong hands and gets power-cycled, an attacker has to guess a 20+ character passphrase as opposed to a 4-8 digit PIN.

    The ugly: Just the /data filesystem is encrypted. If you have a SDcard, you are SOL unless you have a Motorola device that has their own file based mechanism of writing encrypted data.

    As for iOS, AFAIK, it mainly relies on hardware chip voodoo to only allow access to the AES key once the chip validates the PIN, and to mitigate an attack against just four digits (which is the typical PIN code length.) If one of the chips has a weakness, game is over.

    With the latest devices, both iOS and Android are decently secure, except both have strengths weaknesses. Android can be set to have a reasonably strong passphrase, then use a PIN once /data is mounted. However, Android can't encrypt SD cards. iOS is encrypted immediately, but the downside is that the OS relies on magic smoke ASICs to enforce its security.

  • by icebike (68054) on Tuesday April 02, 2013 @05:47PM (#43343003)

    When you do read TFA you find out this:

    Take the two Motorola devices(android). Both were wiped, and neither had much to speak of stored in their built-in memory, just some application data with no personally identifiable fingerprints.

    But one user left his micro SD card in the phone. Although the contents of the card were deleted, the card had not been formatted. This, apparently, meant the files were recoverable. And because Android cached application data to this SD card, Reiber could recover e-mail data as well — enough that we could positively identify the phone’s owner via his e-mail address. But the real treasure trove was the photos and documents. The photos still had metadata, including the dates, times and locations in which the photos were shot. And while the documents were benign, if the phone’s owner had stored sensitive information on his phone — think a tax return with a Social Security number, or a .pdf bank statement — we would have had that, too.

    So other than USER Stupidity of leaving his SD card in the device he recycled, this once again is an Apple story pinned to a model long out of production dating to a problem long since fixed by Apple.

    Not that it changes much, if the police who buy these forensic tools happen to get your phone they pretty much have everything they need to know everything about you. How does "AccessData" get around violations of the DMCA by building tools to circumvent encryption?

  • by Anonymous Coward on Tuesday April 02, 2013 @06:39PM (#43343415)

    Once again, blackberries solved this problem about 10 years ago (or more).

    If you want real, audited, certified security, get a blackberry.

    If security isn't important to you, android & iphone are fine.

    Sadly, most people are in the latter category.

Old programmers never die, they just hit account block limit.

Working...