• halfmoon
    User Attivo •

    Tik Tok: la clipboard degli iPhone, e il reverse engineer che rivela gli abusi sui dati degli utenti

    Ieri mi è capitato sotto mano un articolo che parlava di Tik Tok e del suo modo di operare su iPhone che gli permetteva di spiare il contenuto degli appunti degli utenti ,
    oggi scopro di un utente che avrebbe fatto reverse engineer scoprendo che la APP ha fondamentalmente un lato utente carino che fa leva sulla facilità di editing video, dall'altro lato c'è un "backend" che è scritto in modo da raccogliere quanti più dati possibile, senza suppongo alcun consenso. Noi che siamo del settore possiamo evitare di usarlo con consapevolezza, ma il resto del mondo?

    Qui il link a Reddit sul tema del reverse engineering

    *So I can personally weigh in on this. I reverse-engineered the app, and feel confident in stating that I have a very strong understanding for how the app operates (or at least operated as of a few months ago).

    TikTok is a data collection service that is thinly-veiled as a social network. If there is an API to get information on you, your contacts, or your device... well, they're using it.

    Phone hardware (cpu type, number of course, hardware ids, screen dimensions, dpi, memory usage, disk space, etc)

    Other apps you have installed (I've even seen some I've deleted show up in their analytics payload - maybe using as cached value?)

    Everything network-related (ip, local ip, router mac, your mac, wifi access point name)

    Whether or not you're rooted/jailbroken

    Some variants of the app had GPS pinging enabled at the time, roughly once every 30 seconds - this is enabled by default if you ever location-tag a post IIRC

    They set up a local proxy server on your device for "transcoding media", but that can be abused very easily as it has zero authentication

    The scariest part of all of this is that much of the logging they're doing is remotely configurable, and unless you reverse every single one of their native libraries (have fun reading all of that assembly, assuming you can get past their customized fork of OLLVM!!!) and manually inspect every single obfuscated function. They have several different protections in place to prevent you from reversing or debugging the app as well. App behavior changes slightly if they know you're trying to figure out what they're doing. There's also a few snippets of code on the Android version that allows for the downloading of a remote zip file, unzipping it, and executing said binary. There is zero reason a mobile app would need this functionality legitimately.

    On top of all of the above, they weren't even using HTTPS for the longest time. They leaked users' email addresses in their HTTP REST API, as well as their secondary emails used for password resets. Don't forget about users' real names and birthdays, too. It was allllll publicly viewable a few months ago if you MITM'd the application.*

    2
Effettua l'accesso per rispondere