Issue metadata
Sign in to add a comment
|
Chrome for Android - Bad eliding of HTTP URLs allows for URL Spoofing
Reported by
luan.her...@hotmail.com,
Apr 23 2016
|
||||||||||||||||||||||||
Issue descriptionVULNERABILITY DETAILS For some reason the eliding of HTTP URLs behave differently from the HTTPS ones. If the URL utilizes HTTP, the alignment happens left-to-right, displaying first the subdomains and then the origin. With this, the attacker can craft a URL with several subdomains and the origin eventually will be hidden, like in: http.png (Full URL: http://www.developers.facebook.com.lbherrera.me) This doesn't happens if HTTPS is utilized, as the alignment starts from right-to-left, displaying first the origin and then the subdomains, thus preventing the URL from being spoofed. See https.png (Full URL: http://www.developers.facebook.com.lbherrera.me) VERSION I tested on: Chrome 49.0.2623.105 / Android 5.1.1 Chrome 49.0.2623.105 / Android 4.4.2 REPRODUCTION CASE 1. Access http://www.developers.facebook.com.lbherrera.me on Chrome for Android and check the omnibox. 2. Access https://www.developers.facebook.com.lbherrera.me on Chrome for Android and check the omnibox.
,
Apr 23 2016
,
Apr 25 2016
,
Apr 25 2016
,
Apr 26 2016
Tentatively adding medium severity. Feel free to update this if you disagree.
,
Apr 26 2016
,
Apr 26 2016
Hmm, this bug seems to differ between http and https. I'll let palmer comment.
,
Apr 26 2016
,
Apr 26 2016
,
May 6 2016
,
May 7 2016
palmer: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 21 2016
palmer: Uh oh! This issue still open and hasn't been updated in the last 28 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 25 2016
,
Oct 2 2016
,
Jun 29 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vakh@chromium.org
, Apr 23 2016Owner: palmer@chromium.org