News for hackers. Stuff that matters.
Re:The target=“_blank” vulnerability by example by 0xmohit on Monday August 29, 2016 @05:15AM (#12380838)
- Interesting that this has been posted six times [0] over the past 4 days

- Earlier discussion [1] on the same topic posted elsewhere

[0] https://news.ycombinator.com/from?site=dev.to

[1] https://news.ycombinator.com/item?id=11631292

Re:The target=“_blank” vulnerability by example by amgin3 on Monday August 29, 2016 @05:29AM (#12380868)
Most organizations don't see this as a valid vulnerability. If you read terms of most bug bounty programs, they almost always specify that window.opener is out of scope.
Re:The target=“_blank” vulnerability by example by andy_ppp on Monday August 29, 2016 @07:25AM (#12381184)
Why on earth does target="_blank" expose window.opener to the new page - that opens up some mad tracking possibilities if you have JS in the opened page (e.g. Analytics or comments).

Seems the default should be rel="noopener"...

Re:The target=“_blank” vulnerability by example by andy_ppp on Monday August 29, 2016 @10:00AM (#12381871)
I've worked out why this is allowed... if you middle click (open in a new tab) a pop up that uses a link (but intercepts the event by default) window.opener will still work in the new tab. The sibling is right, this should be same domain only.
Re:The target=“_blank” vulnerability by example by methyl on Monday August 29, 2016 @08:32AM (#12381404)
At least for cross-domain URLs.
Re:The target=“_blank” vulnerability by example by endemic on Monday August 29, 2016 @10:48AM (#12382176)
Wow, I never knew about this API. Seems very ripe for exploitation; check the referrer for an incoming request and route the other tab to a mirrored version of the site, on a host you control, preferably with a "you've been logged out due to inactivity, enter your credentials" modal.
Re:The target=“_blank” vulnerability by example by endemic on Monday August 29, 2016 @02:14PM (#12383890)
Another demo page, with links to open bugs in various browsers: https://mathiasbynens.github.io/rel-noopener/ (not all browsers implement the `rel="noopener"` attribute)
Re:The target=“_blank” vulnerability by example by helthanatos on Monday August 29, 2016 @08:01AM (#12381288)
I wonder how much work it would take to get real information...
Re:The target=“_blank” vulnerability by example by Kenji on Monday August 29, 2016 @09:16AM (#12381618)
I followed the three steps below "To clarify" multiple times in different browsers and (3) did not work at all. I don't see the problem. This article has left me confused.

EDIT: Oh, seems like Instagram has fixed this after all. If you inspect the link on his Instagram profile, you will find rel="nofollow me noopener noreferrer" and if you remove that attribute, it works just as described in the blog. I learned something new.

Re:The target=“_blank” vulnerability by example by jldteixeira on Monday August 29, 2016 @09:19AM (#12381632)
Seems to be fixed now. On Instagram the link has rel="nofollow me noopener noreferrer"
Re:The target=“_blank” vulnerability by example by kedean on Monday August 29, 2016 @08:24PM (#12386485)
As of right now, the exploit still works on Facebook. The article links to the example there.