Live data from Hacker News

Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

bugs.chromium.org

61–70 of 86 posts

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#63
post #3

Warning: if you do this on your Android phone at the moment, you may have to completely clean your Chrome application storage to be able to use the app afterwards.

> Note: this is even worse if the URL was opened from an intent. In that case, Chrome can end up completely bricked because upon restart it will immediately attempt to re-open the URL that crashed it. I could not recover from this without having to fully "Clear Storage". Too late for me. Not even from intent. Chrome force stop later, it still tries to load it and immediately crashes.

Can you clear the app data via adb?

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#64
post #56
post #53

Earlier quoted context omitted.

That’s not the point, and sarcasm is uncalled for.

That's not sarcasm. Because this feature is missing on chrome android I only have the option to close all tabs or to manually open each tab and decide to bookmark it or not.

Ah, sorry. I was thinking of desktop browsers that do have the feature (but I don’t think I’ve ever used it as, well, I hardly use bookmarks).

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#65

Works as expected on Brave (it's Chromium based)

You mean bricking/crashing or nothing ?

The bug report contains expected result "DNS resolution error, or some kind of non-fatal error in general." - so that's what I meant by works as expected. It just shows DNS failure page, it does not crash the browser.

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#66
Surprised this wasn't submitted or treated by Google as a security defect. I don't think Google pays out for DoS typically, but considering how easily this can be weaponized, this one probably should've paid out.

Especially if the mechanism of the crash also allows for an RCE that hasn't been discovered yet. Worth equipping fuzzers with the URL as a prefix.

Edit: They reclassified it as a security defect and restricted permissions on it after my comment directly on the bug.

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#67
post #66

Surprised this wasn't submitted or treated by Google as a security defect. I don't think Google pays out for DoS typically, but considering how easily this can be weaponized, this one probably should've paid out. Especially if the mechanism of the crash also allows for an RCE that hasn't been discovered yet. Worth equipping fuzzers with the URL as a prefix. Edit: They reclassified it as a security defect and restrict…

Absolutely. I'm surprised this isn't marked as critical.

If this was included in malicious emails and texts, it would block the use of Chrome on Android completely and the only current fix is to clear all browser data i.e. bookmarks, passwords etc.

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#69
post #3

Earlier quoted context omitted.

> Note: this is even worse if the URL was opened from an intent. In that case, Chrome can end up completely bricked because upon restart it will immediately attempt to re-open the URL that crashed it. I could not recover from this without having to fully "Clear Storage". Too late for me. Not even from intent. Chrome force stop later, it still tries to load it and immediately crashes.

Can you clear the app data via adb?

Could not be bothered to try (my daily driver on Android is Firefox)

Re: Opening http://../foo on Android Chrome crashes the browser (Warning: or worse)

#70
post #22

Earlier quoted context omitted.

Clearing cache was sufficient enough for me to launch Chrome and quickly close the tab.

I just closed chrome, reopened hit and immediately hit the home button at the top left. That was enough to get me to safety.

Thanks for this, but I needed to disable animations in accessibility for this to work.
Post reply on HN