When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
Hi @APrieto034095 (Community Member) ,
In general we recommend that you apply the "X-Content-Type-Options" header with the "nosniff" header broadly across your domain. In general you should not be relying on 'mime type sniffing' and as such should be able to send this header out for every response. This will automatically close the flaw on rescan.
You can read more on the purpose of this header over on Stack Overflow: https://stackoverflow.com/a/37201425/4512 .
The risk from missing this header is low in general as it is more a defense-in-depth technique, and if the static file is properly administrator controlled an attacker may not be able to modify it. But not having this header on all responses from your application is an indication that it is not globally configured and there may be other, more risky exploit paths that we are unable to see in our Dynamic Analysis.
Thank you,
Boy Baukema