| Who needs SWATing when you can send a CP pic (either real or with hash collision as per the thread few days ago) from a virtual overseas number/service and get FBI van to show up as well? What about injecting code into a public website to download same pic into local browser cache without user’s knowledge? The simplicity of the attack vectors here that would trigger the “manual” investigation is just dumbfounding and ripe for abuse/misuse. |
> The executives acknowledged that a user could be implicated by malicious actors who win control of a device and remotely install known child abuse material. But they said they expected any such attacks to be very rare and that in any case a review would then look for other signs of criminal hacking.
What triggers them to look for signs of criminal hacking?
Does every manual review process involve such checks?
Are they searching device backups for indicators of compromise [IoC]?
What if there's no device backup or device image to scan?
What if the scan fails to notice IoC?
What if the device was compromised after the last backup?
What if the device was compromised via physical access?
What if the device isn't compromised and the material was pushed maliciously or via drive-by download?
It's dangerous to assume that all material on a network-connected device arrived with the consent of the user when it can accept incoming messages from strangers, trick people into downloading files, or be compromised without your knowledge.
“That isn't mine” is going to be a tough defence if you can't even take measures to log where content came from.
Client-side scanning seems to amplify this issue (which could still happen with cloud storage) because at least cloud storage doesn't generally ship with or integrate deeply with messaging apps, social media, a web browser, QR codes, App Clip Codes[1] etc.
The impact might be fairly low right now with the current proposal (images would have to be uploaded to iCloud, so cached browser images don't get scanned as far as we know), but the existence of the non-consensual scan in the first place is worrying, because it means such attacks are only a policy change away.
[1] : https://developer.apple.com/design/human-interface-guideline...