HTTP X Protection Headers - Microsoft Google Stringency
The terminology states that HTTP has X Factor protection considering the protection parameters implemented at the HTTP base level. Steps are taken to improve the functionality by inculcating the HTTP headers and applying it at the real time environment.
Looking at this scenario , I triggered my emulator with perl as base to write some lines of code to check the GWS server by Google at port 80.
[Google Check]
C:\Perl\bin>perl http_X_enum.pl google.com
(*) http_X_enum.pl - HTTP[X] protection enumerator
(*) enumerates (clickjacking,mime sniffing,xss protection, content download , csp etc) applied defense.
(*) web application security assessment script
(*) written by 0kn0ck [at] secniche.org
(*) checking the state of server through icmp requests.
(*) google.com is subjected to be alive
Server: gws
[+] ++++++++++++++++++++++++++++++++++++++++++++++++++++
[+] checking for applied defense on domain : google.com
[+] ++++++++++++++++++++++++++++++++++++++++++++++++++++
[+] detected possible [X-XSS-Protection: 0 ] xss protection parameter : X-XSS-Protection: 0
[-] http parameter [X-XSS-Protection: 1] defense is not applied at domain.
[-] http parameter [X-FRAME-OPTIONS: DENY] clickjacking defense is not applied
[-] http parameter [X-FRAME-OPTIONS: SAMEORIGIN] clickjacking defense is not applied
[-] http parameter [X-CONTENT-TYPE-OPTIONS: NOSNIFF] mime handling-sniffing opt out is not applied
[-] http parameter [X-DOWNLOAD-OPTIONS: NOOPEN ] mime handling- download force save is not applied
[-] http parameter [X-CONTENT-SECURITY-POLICY: ALLOW SELF] content policy is not applied.
[-] http parameter [X-CONTENT-SECURITY-POLICY: ALLOW https://self] content policy is not applied.
[-] http parameter [ACCESS-CONTROL-ALLOW-ORIGIN] csrf origin access is not applied.
=================[DEBUG]=============================
HTTP/1.1 301 Moved Permanently
Location: http://www.google.com/
Content-Type: text/html; charset=UTF-8
Date: Wed, 25 Nov 2009 02:38:09 GMT
Expires: Fri, 25 Dec 2009 02:38:09 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 219
X-XSS-Protection: 0
=================[DEBUG]=====================
[+] execution success.
Lets; see Yahoo
C:\Perl\bin>perl http_X_enum.pl yahoo.com
(*) http_X_enum.pl - HTTP[X] protection enumerator
(*) enumerates (clickjacking,mime sniffing,xss protection, content download , csp etc) applied defense.
(*) web application security assessment script
(*) written by 0kn0ck [at] secniche.org
(*) checking the state of server through icmp requests.
(*) yahoo.com is subjected to be alive
[+] +++++++++++++++++++++++++++++++++++++++++++++++++++
[+] checking for applied defense on domain : yahoo.com
[+] +++++++++++++++++++++++++++++++++++++++++++++++++++
[-] http parameter [X-XSS-Protection: 0] not detected.
[-] http parameter [X-XSS-Protection: 1] defense is not applied at domain.
[-] http parameter [X-FRAME-OPTIONS: DENY] clickjacking defense is not applied
[-] http parameter [X-FRAME-OPTIONS: SAMEORIGIN] clickjacking defense is not applied
[-] http parameter [X-CONTENT-TYPE-OPTIONS: NOSNIFF] mime handling-sniffing opt out is not applied
[-] http parameter [X-DOWNLOAD-OPTIONS: NOOPEN ] mime handling- download force save is not applied
[-] http parameter [X-CONTENT-SECURITY-POLICY: ALLOW SELF] content policy is not applied.
[-] http parameter [X-CONTENT-SECURITY-POLICY: ALLOW https://self] content policy is not applied.
[-] http parameter [ACCESS-CONTROL-ALLOW-ORIGIN] csrf origin access is not applied.
=====================[DEBUG]=====================
HTTP/1.1 301 Moved Permanently
Date: Wed, 25 Nov 2009 02:42:40 GMT
Location: http://www.yahoo.com/
Cache-Control: private
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
95 The document has moved here.
0
==================[DEBUG]======================
[+] execution success.
The script posed the appropriate results looking at the two different domains. But one thing is sure that Google is not at all in coherence with Microsoft steps.
Posted on 11/24/2009 06:25:00 PM by 0kn0ck | 0 Comments
![]()
![]()




















