3 ms·
Here is one: http://arstechnica.com/security/2015/04/no-joke-googles-april-fools-prank-inadvertently-broke-sites-security/ http://arstechnica.com/security/2015/
by kuschku 11y ago
Here is one: http://arstechnica.com/security/2015/04/no-joke-googles-april-fools-prank-inadvertently-broke-sites-security/ http://arstechnica.com/security/2015/04/no-joke-googles-apri...
The issue was that they wanted to load the page – with the user logged in, etc – on com.google. For this they implemented an explicit URL parameter that would allow this.
- magicalist 11y ago> Attackers could have seized on the omission of the X-Frame-Options header to change a user's search settings, including turning off SafeSearch filters The horror!