lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date: Tue, 12 Apr 2016 15:03:06 GMT
Subject: Open redirect on

An open redirect is operating at

Google’s main website provides a subsite for displaying mobile-optimized pages published using a special subset of HTML called AMP. While this works for mobile devices, for non-mobile devices, this redirects to the original site, thus resulting in an open redirect. 

The subsite operates at the following URL:

where XXXX is the URL of the site. 

Here is an example of a legit URL&#8202;—&#8202;in mobile browsers this would display the actual article (this can simulated using Chrome’s developer tools):

HOWEVER, on non-mobile devices this would redirect to:

Because the vendor accepts any site without whitelist, this can be used as an open redirect. Additionally, since this is hosted on the same main domain as the search engine, it can in theory be used to drive XSS or other similar attacks, although this is mitigated by the fact that AMP currently does not allow Javascript.

Vendor Response
The vendor communicated that they do not consider open redirects to be a security issue

Google Security CID: 7–2623000011032
AMP site:
Vendor’s view on open directs:

2016–04–07: Vendor notified
2016–04–07: Vendor response
2016–04–11: Public disclosure

Powered by blists - more mailing lists