Leaked Cellebrite Tool Docs Reveal List of Phones That Can Be Unlocked

Comments

• Lojcs@lemm.ee ⁨3⁩ ⁨months⁩ ago

  Mfw Samsung on android 6 is the most secure 😮. Wonder if it has something to do with the mid boot password option that was around

  source

  • woelkchen@lemmy.world ⁨3⁩ ⁨months⁩ ago

    Mfw Samsung on android 6 is the most secure 😮. Wonder if it has something to do with the mid boot password option that was around

    More likely: So old, no point in even attempting, therefore not supported.

    source

    • WhatAmLemmy@lemmy.world ⁨3⁩ ⁨months⁩ ago

      Security through insecurity. Lol.

      source
  • henfredemars@infosec.pub ⁨3⁩ ⁨months⁩ ago

    I think it’s probably a demand issue. There’s just not that many devices running with that Android version, and it takes a lot of time and money to pay engineers to find and use extremely complex state of the art exploits.

    source

    • pineapplelover@lemm.ee ⁨3⁩ ⁨months⁩ ago

      So security through obscurity

      source

      • -> View More Comments
• mctoasterson@reddthat.com ⁨3⁩ ⁨months⁩ ago

  Nice to see some benefit to updated vanilla AOSP, Graphene, and other options.

  It goes without saying but it seems like a deeply fucked business model to horde zero-days that could cause billions in damage or safety issues if they fall into the wrong hands, in order to keep your mercenary surveillance product working.

  source
• helenslunch@feddit.nl ⁨3⁩ ⁨months⁩ ago

  The document also specifically mentioned GrapheneOS

  Okay…what’d it say? Baffling that the author didn’t think that was important…

  source

  • ExtravagantEnzyme@lemm.ee ⁨3⁩ ⁨months⁩ ago

    I mean, the doc’s are available through the link. But here’s some screen grabs: Image

    Image

    AFU: After First Unlock BFU: Before First Unlock BF: Brute Force FBE: File Based Encryption FDE: Full Device Encryption FFS: Full File System

    source

    • peopleproblems@lemmy.world ⁨3⁩ ⁨months⁩ ago

      :(

      source

      • -> View More Comments
    • helenslunch@feddit.nl ⁨3⁩ ⁨months⁩ ago

      The only docs I saw pertained to iOS.

      source

      • -> View More Comments
  • Lojcs@lemm.ee ⁨3⁩ ⁨months⁩ ago

    It says it’s immune since 2023 updates

    source

    • helenslunch@feddit.nl ⁨3⁩ ⁨months⁩ ago

      Nice, thanks

      source
• Adanisi@lemmy.zip ⁨3⁩ ⁨months⁩ ago

  Use a long password and you’ll be immune from their before first unlock brute force.

  Passcodes are trivial to break.

  source

  • underisk@lemmy.ml ⁨3⁩ ⁨months⁩ ago

    They’re exploiting vulnerabilities and back doors not brute forcing your passcode. The only way you’re keeping them out is with hardware encryption which the iPhone has and why it’s apparently the only one not vulnerable. Hardware encryption also won’t matter if your vendor shares their keys with law enforcement which as far as I’m aware Apple is the only one that has been taken to court for refusing.

    Don’t put anything incriminating on your phones.

    source

    • Adanisi@lemmy.zip ⁨3⁩ ⁨months⁩ ago

      In a before-first-unlock state they absolutely are bruteforcing, since the filesystem is encrypted. The exploits are for bypassing the retry limit in that case.

      source
    • fmstrat@lemmy.nowsci.com ⁨3⁩ ⁨months⁩ ago

      Huh? None of this makes sense to me. Apple and Google do not have encryption keys for your device, regardless of hardware or software. When your phone is unlocked, the key and/or hash is in memory, and may be key wrapped, regardless of hardware or software. iOS is listed as vulnerable to the attacks, minus the latest devices and versions, which is pretty much the norm with lagging development. Same woth latest Pixels. Where are you getting this info from?

      source

      • -> View More Comments
  • fmstrat@lemmy.nowsci.com ⁨3⁩ ⁨months⁩ ago

    Incorrect. Read the links.

    source