Email or username:

Password:

Forgot your password?
Top-level
Pierre Bourdon

Another one showing how a smaller crop can end up revealing even more of the original screenshot image.

13 comments
marnanel

@delroth the people who run that site are going to be receiving an awful lot of other people's sensitive information

Pierre Bourdon

@marnanel it's all client side, nothing gets uploaded. At least in its current version I was using.

:jan:‍:abreath:‍‍🌬:dandelion:

@delroth I've noticed something that might be related. this may explain how they can have the "save vs save as" option when making small changes like a crop or "enhance" photo edits. If you pick save, it doesn't make a new file but must save the image adjustment data in a similar manner. I'm sure digging into a larger data sample size could turn up some more info

Example Google Photos save edits screen
Pierre Bourdon

@Crazypedia that's the Google Photos crop tool which I'm pretty sure is different from the screenshot crop tool (and not vulnerable).

Pierre Bourdon

PoC author @retr0id published his writeup about how the bug was found, I strongly encourage you to give it a read and a follow: da.vidbuchanan.co.uk/blog/expl

Émilie Fecteau

@delroth If iOS has a similar bug, I am screwed, lol. But I’ve always thought something like this *might* be possible, so maybe it’s fine.

gudenau

@delroth @retr0id For some reason all of the screenshots I've tried just do this. Any idea why that might be the case? I'm on a Pixel 4 XL.

David Buchanan
@gudenau @delroth Good question, I don't have an easy way to debug, but what happens if you use my python script? (it's linked in the blog post)
Erik Haugen

@delroth Yeah, without being a zlib expert, I think the smaller the crop the more likely the original is recoverable.

Go Up