Hash collision in Apple NeuralHash model

Re:Hash collision in Apple NeuralHash model by yayr on Wednesday August 18, 2021 @05:29PM (#28227426)

If anybody with enough motivation can modify any existing harmless image to have the same neural hash as a "tracked database" image this will create too many false positives. Too many false positives make the algorithm useless.

If someone with even more motivation and the means to put those images onto your device via social engineering, exploits or maybe even features and you become the target of a criminal investigation in any jurisdiction you just happen to be at the moment, this makes the algorithm harmful.

[ Parent | on HN ]

Re:Hash collision in Apple NeuralHash model by FabHK on Wednesday August 18, 2021 @08:08PM (#28228811)

> this will create too many false positives. Too many false positives make the algorithm useless

Apple can (and will) run a second algorithm server side to filter out further false positives.

> If someone with even more motivation and the means to put those images onto your device via social engineering, exploits or maybe even features

Such an attacker could just plant CSAM directly. The hash collision has no bearing on it. If, however, it is hash collision you're worried about, they'd be caught during the manual review.

[ Parent | on HN ]