7 ms·
If you look at the source, they're actually disabling the XSS protections in the browser: # Disable the reflected XSS filter for demonstration purposes self.r
by fastest963 10y ago
If you look at the source, they're actually disabling the XSS protections in the browser:
# Disable the reflected XSS filter for demonstration purposes
self.response.headers.add_header("X-XSS-Protection", "0")
- dylanfw 10y agoChrome's XSS filter can still be circumvented in quite a few instances. The easiest way I've seen is when the attacker controls at least two variables and can split the XSS across them in such a way that neither half appears malicious but when loaded into the page they create a malicious script. Example: ?a=<script>void('&b=');alert('XSS')</script> The value of a is <script>void(' and the value of b is ');alert('XSS')</script>.