This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of ".NET AntiXSS Library"

From OWASP
Jump to: navigation, search
m (XSS References)
(added HtmlSanitizer)
Line 21: Line 21:
 
*OWASP Anti-Samy Library (https://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project_.NET)
 
*OWASP Anti-Samy Library (https://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project_.NET)
 
**Not recently maintained (good option for to get it up to date and relevant!!!)
 
**Not recently maintained (good option for to get it up to date and relevant!!!)
 +
* HtmlSanitizer
 +
** A open-source .Net library.
 +
** The HTML is cleaned with a white list approach.
 +
** All allowed tags and attributes can be configured.
 +
** The library is unit tested with the [https://www.owasp.org/index.php/XSS_Filter_Evasion_Cheat_Sheet OWASP XSS Filter Evasion Cheat Sheet]
 +
** https://github.com/mganss/HtmlSanitizer
  
 
== XSS References ==
 
== XSS References ==

Revision as of 23:00, 2 March 2015

NOTE: This content is a work in progress and all contribution is welcome. Please contact Jeff Knutson with questions, ideas, corrections, etc.

Overview

Cross site scripting (XSS) continues to show up on the as a top vulnerability every year. While very pervasive and dangerous, this vulnerability is possible to mitigate with reasonable developer effort. This page is dedicated to helping mitigate this vulnerability in regards to the Microsoft .NET Framework.

Attack Vectors

The primary XSS attack vectors are:

  • Reflected XSS
  • Persistent XSS

Please see Cross-site Scripting (XSS) for more detail regarding reflected and persistent XSS attacks.

Options

XSS References

TODO

Now

  • Look at the Microsoft implementations
  • See what work has already been done in the OWASP space for XSS
  • See what other work has been done for XSS (both .NET and other technology stacks)
  • Illustrate vulnerabilities and how to mitigate them (e.g. WebGoat.NET)
  • See if we can get the OWASP Anti-Samy project back into relevance

Future

  • Dream big here!