The Anti-MIME-Sniffing header X-Content-Type-Options was not set to ‘nosniff’.
The Anti-MIME-Sniffing header X-Content-Type-Options was not set to ‘nosniff’. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.
Ensure that the application/web server sets the Content-Type header appropriately and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages. If possible, ensure that the end-user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/webserver to not perform MIME-sniffing.
Run our automated penetration testing and vulnerability assessment to protect your web application from hackers.
The web/application server is leaking information via one or more “X-Powered-By” HTTP response headers.