New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 875260 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Bug



Sign in to add a comment

Pop-up blocker string in Portuguese can lead to confusion about whether URL refers to pop up, or page that triggered it (Was: Hijacking Clicks)

Reported by adri...@brztec.com, Aug 17

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
Hi team. I found a way to hijack clicks, tricking users to click in trusted URLs but openning others destinations.

1. Open the attached poc.
2. Mouse over the link and you see https://www.google.com showing that the correct link.
3. Click in the link and a new tab will be openned with https://www.marvel.com.
4. Click in the parent tab and click in the pop-up blocker icon and you will see https://www.google.com has been blocked.

*** PoC Code ***

<a id="link1" name="link1" href="https://www.google.com"  onclick="onMouseClick()" target="_blank">www.google.com</a>

<script>
function onMouseClick(){
	var newdestiny = window.open("about:blank", "link1");
	newdestiny.document.write('<script>document.location.href="https://www.marvel.com";</' + 'script>');
	setTimeout(function(){ 
		//newdestiny.close();
	}, 1000);
}
</script>

What is the expected behavior?
The window opened from window.open() should be blocked and not the destiny from href attribute.

What went wrong?
Apparently chrome makes confusion about which destination should be blocked.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: n/a
OS Version: 10.0
Flash Version:
 
Google_Chrome_Pop-up_config.JPG
46.7 KB View Download
PoC.JPG
95.1 KB View Download
PoC_results.JPG
108 KB View Download
poc_clickjacking.html
391 bytes View Download
Cc: chromelocalization@google.com
Components: UI>Localization UI>Browser>PopupBlocker
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam OS-Android OS-Chrome OS-Fuchsia OS-Linux OS-Mac Type-Bug
Summary: Pop-up blocker string in Portuguese can lead to confusion about whether URL refers to pop up, or page that triggered it (Was: Hijacking Clicks) (was: Hijacking Clicks)
Regarding the Status Bubble, it is not a security surface, so the fact that that URL is spoofed is not considered a bug in this case (see https://www.chromium.org/user-experience/status-bubble). 

Regarding the pop-ups blocked notification, it looks that is working correctly too, the highlighted part is the URL of the site that would have showed in the popup, which is correctly set to google.com in this case, the page that triggered the popup is shown below in the "Always allow pop-ups from http://localhost" which is also correct.

However, it seems this might be a localization issue, in the English version, the text shows as "Pop-ups blocked: <list of pop up URLS>", while in Portuguese it is shown as "Os seguintes pop-ups foram bloqueados nesta pagina: <list of pop up URLS>" which translates to "The following pop-ups have been blocked in this page: <list of pop up URLS>", so I can understand that can be confusing, particularly when only one URL is shown, it looks like the blocked URL refers to the site that triggered the popup. Adding the localization component (and renaming the issue) regarding the confusing string.
Owner: jdignos@chromium.org
Status: Assigned (was: Unconfirmed)
Routing to jdignos@chromium.org

Hi! I made more tests and the strange behavior occurs only in some javascripts events. For example, when event is onmousedown the href value isn't related in pop-up blocker, but if the event is onmouseup or onclick it is will be related in pop-up blocker. In onwheel or onmousemove href isn't related but all pop-ups will be blocked.

<a id="link5" name="link5" href="https://twitter.com"  onmousedown="onMouseClick2();" target="_blank">twitter.com</a>
<script>
function onMouseClick2(){ var popup3 = window.open('https://www.marvel.com', '_blank'); popup1 = window.open('https://www.dccomics.com', '_blank'); }
</script>


more_tests.JPG
24.7 KB View Download
Cc: jdignos@chromium.org
Owner: melliem@google.com
Hi Mellie,

Need you help on this bug.

Thanks!
Owner: robliao@chromium.org
hi, this is a bit confusing for our localization team. Would you be able to help us identify where exactly the translation issue is coming from so we can more easily identify it in TC? Thanks a lot!
Owner: melliem@google.com
https://bugs.chromium.org/p/chromium/issues/detail?id=875260#c1 (Comment 1) suggests the localization issue:

However, it seems this might be a localization issue, in the English version, the text shows as "Pop-ups blocked: <list of pop up URLS>", while in Portuguese it is shown as "Os seguintes pop-ups foram bloqueados nesta pagina: <list of pop up URLS>" which translates to "The following pop-ups have been blocked in this page: <list of pop up URLS>", so I can understand that can be confusing, particularly when only one URL is shown, it looks like the blocked URL refers to the site that triggered the popup. Adding the localization component (and renaming the issue) regarding the confusing string.

Cc: carlosil@chromium.org
Looking in the translation console 6815484526221703469 for Chrome seems to be the corresponding message (no link due to this being a public bug). I do not see the corresponding Portuguese translation identified by #1.

CC'ing carlosil@chromium.org for further clarification.
That's strange, I also checked https://cs.chromium.org/chromium/src/chrome/app/resources/generated_resources_pt-BR.xtb and https://cs.chromium.org/chromium/src/chrome/app/resources/generated_resources_pt-PT.xtb and I can't see the string that shows up in the picture, but 'Pop-ups bloqueados' which lines up with the English string, I wonder if this was changed in a version newer than what the original reporter was using. If so, this is probably a wontfix.
Owner: jdignos@chromium.org
Hey Joshua, could you have a look at TC now that we have more details?
Status: WontFix (was: Assigned)

Sign in to add a comment