![]() | |
| |||||||
| Home | Register | Projects | Blogs | FAQ | Calendar | Search | Today's Posts | Mark Forums Read | Free Directory | Free DNSReport | Tags |
| Notices |
| Security discussions Discuss about the computer security in general |
NoScript features unique Anti-XSS counter-measuresThis is a discussion on "NoScript features unique Anti-XSS counter-measures" within the Security discussions part of the Computer Security: Discussions section; Since today the NoScript addon of Firefox added an interesting feature wich blocks the XSS attacks. Anti-XSS protection Cross-Site Scripting (XSS) vulnerabilities are usually caused programming errors made by web developers, allowing an attacker to inject his own ... |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| ||||
| Since today the NoScript addon of Firefox added an interesting feature wich blocks the XSS attacks. Anti-XSS protection Cross-Site Scripting (XSS) vulnerabilities are usually caused programming errors made by web developers, allowing an attacker to inject his own malicious code from a certain site into a different site. They can be used, for instance, to steal your authentication credentials and, more in general, to impersonate you on the victim site (e.g. your online banking or your web mail). This kind of vulnerability, often overlooked, is very widespread and becoming highly popular among hackers: someone even bothered to write a JavaScript-based bot, called Jikto, turning your browser into a zombie which relentlessy sends automated XSS attacks all around. Of course this tool has been built "for research purpose", but its code unfortunately appears to be leaked in the wild, so anybody can take advantage of it, now... NoScript XSS notification and its menu NoScript features unique Anti-XSS counter-measures, even against XSS Type 1 attacks targeted to whitelisted sites. Whenever a non-trusted site tries to inject JavaScript code inside a trusted (whitelisted and JavaScript enabled) site, NoScript filters the malicious request neutralizing its dangerous load. Then a yellow notification bar displays a message like "NoScript filtered a potential cross-site scripting (XSS) attempt from [some-evil-url.com]. Technical details have been logged to the Console." On the left side of this bar there's also an "Options..." button: if you click it, you can choose among the following actions: * Show Console, displaying the Error Console where further technical details about the actions taken by NoScript are logged. Please notice that the Error Console is a standard Firefox component reporting every JavaScript-related message from any source: the explanatory messages specifically coming from NoScript and related to XSS are only the ones marked with a [NoScript XSS] label. * Unsafe Reload, which will "replay" the requst bypassing XSS filters. Use this command only if you're absolutely sure that NoScript detected a false positive. * Suppress the XSS-related notifications (you will still be able to operate through the standard NoScript menu). * Open the XSS Options panel. * Navigate to the XSS FAQ web page. The specific anti-XSS counter-measures are controlled by two options under NoScript Options|Advanced|XSS. Both these options are enabled by default for your maximum protection. NoScript's anti-XSS filters had been deeply tested and proved their ability to defeat every known reflective XSS technique, but their power is a double-edged sword: sometime they may detect a weird looking but legitimate request as a "potential XSS attempt". This should almost never be a show stopper, since the filter most of the time doesn't prevent you from navigating the filtered page, but the aforementioned Unsafe reload command and the XSS Advanced Options are have been made easily accessible so you can work-around if you hit a false positive with side effects. Just please notify me when it happens, possibly reporting the messages NoScript logged, so I can keep tweaking NoScript's "XSS sensibility" as needed. While Cross-Site Scripting (XSS) vulnerabilities need to be fixed by the web developers, users can finally do something to protect themselves: NoScript is the only effective defense available to "web-consumers", waiting for "web-providers" to clean up their mess. http://noscript.net/?ver=1.1.4.8.070423 |
| Sponsor | ||
| ||
| |
![]() |
| | |
| antixss, countermeasures, features, noscript, unique | |
| Thread Tools | |
| Display Modes | |
| |