News for hackers. Stuff that matters.
Re:Chrome 61 UXSS (CVE-2017-5124) by rraval on Tuesday November 14, 2017 @11:38AM (#15696553)
This seems to be explained in better detail by https://bo0om.ru/chrome-and-safari-uxss. Working via Google Translate, the claim seems to be that using MHTML and XSLT allows you to bypass the sandboxing rules and inject JavaScript that bypasses the same-origin policy.

The linked blog credits a Chromium patch that led to the discovery of this exploit: https://chromium-review.googlesource.com/c/chromium/src/+/65...

Re:Chrome 61 UXSS (CVE-2017-5124) by iancnorden on Wednesday November 15, 2017 @11:42AM (#15705089)
https://securityespresso.org/translations/2017/11/14/chrome-... not sure the accuracy, in case folks can't hit .ru @ work.
Re:Chrome 61 UXSS (CVE-2017-5124) by i_bo0om on Tuesday November 14, 2017 @12:19PM (#15697053)
Wow, nice work)
Re:Chrome 61 UXSS (CVE-2017-5124) by rogerwang on Tuesday November 14, 2017 @07:15PM (#15700500)
This is available before the security issue is expected to be made public in 14 weeks window & exactly why you need to keep whatever Chromium engine in your application up-to-date.