Live data from Hacker News

Accidental Google Pixel Lock Screen Bypass

bugs.xdavidhu.me

341–350 of 475 posts

Re: Accidental Google Pixel Lock Screen Bypass

#342
post #301

Earlier quoted context omitted.

Presumably not all keys? If you receive a phone call while locked presumably the phone can still access the address book to display the contact name and photo? And music playing apps can presumably access their database of music to play songs whilst the phone is locked?

Could be reading a cached copy of the contact list since it’s not very big The music playing is a different story

Text messages (iMessages) can be displayed on lock screens. Not sure how they do that with encryption but maybe the notification is separate.

Re: Accidental Google Pixel Lock Screen Bypass

#344
post #301

Earlier quoted context omitted.

Could be reading a cached copy of the contact list since it’s not very big The music playing is a different story

Text messages (iMessages) can be displayed on lock screens. Not sure how they do that with encryption but maybe the notification is separate.

I think for iMessage, the actual messages are sent using APNS, so the message is in the push notification itself. Thus while you can see the message itself without unlocking, any older messages that are behind the Secure Enclave are inaccessible without keys.

Re: Accidental Google Pixel Lock Screen Bypass

#347

Appalling handling on Google’s end here. The duplicate issue part I can understand, but why should it take two reports of a critical vulnerability to take action? Surely when the first one comes through it’s something you jump on, fix and push out ASAP, not give delay to the point where a second user can come along, find the bug, and report it. The refactor that’s mentioned towards the end of the article is great, bu…

Quoted post unavailable.

No personal attacks, please.

https://news.ycombinator.com/newsguidelines.html

Re: Accidental Google Pixel Lock Screen Bypass

#349

> "Hopefully they treated the original reporter(s) fairly as well." Perhaps they should have reconsidered a bounty payment of some sort for the first bug reporter as well. Perhaps that's where the other $30k of the $100k went. This actually says something interesting about bug bounty programs in general: Given a high level of false positives, it's probably not uncommon AT ALL that sometimes it takes a couple of bug r…

> Given a high level of false positives, it's probably not uncommon AT ALL that sometimes it takes a couple of bug reports before something is reproducible or generates a high enough alert/credibility status, as seemed to have happened here.

This case was not the case of eventually the same reports being taken seriously. None of them were, until the author met people working at Google in person at some event, and him showing them the issue and then persisting.

Different than "Ops, we received a couple of requests, better look into it" and more like "this guy won't stop bothering us about it, probably should look into it".

Security reports from proper pentesters tend to include easy to reproduce steps and if you can't reproduce it yourself from that, you can ask them to expand, since it's in their interest for you to be able to understand them, since that's how they get paid.

Re: Accidental Google Pixel Lock Screen Bypass

#350

Earlier quoted context omitted.

> Keeping the phones on and connected to a charger in the evidence lockers doesn't seem like too much work. There's no way that's a standard procedure.

Why? Seems pretty intuitive to me in a time where everything is encrypted.

If the phone is setup for automatic updates it'll restart within a month (most of the phones I've had do monthly security patches) and you'll be in a fresh boot state. You can't turn off the updates without first unlocking the phone giving you a rather limited window to attempt to exploit the device.
Post reply on HN