OWASP Java HTML Sanitizer Project

= Main = 

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP HTML Sanitizer Project
The OWASP HTML Sanitizer is a fast and easy to configure HTML Sanitizer written in Java which lets you include HTML authored by third-parties in your web application while protecting against XSS. The existing dependencies are on guava and JSR 305. The other jars are only needed by the test suite. The JSR 305 dependency is a compile-only dependency, only needed for annotations. This code was written with security best practices in mind, has an extensive test suite, and has undergone adversarial security review. A great place to get started using the OWASP Java HTML Sanitizer is here: https://github.com/OWASP/java-html-sanitizer/blob/master/docs/getting_started.md.

Benefits

 * Provides 4X the speed of AntiSamy sanitization in DOM mode and 2X the speed of AntiSamy in SAX mode.
 * Very easy to use. It allows for simple programmatic POSITIVE policy configuration (see below). No XML config.
 * Actively maintained by Mike Samuel from Google's AppSec team!
 * Passing 95+% of AntiSamy's unit tests plus many more.
 * This is code from the Caja project that was donated by Google. It is rather high performance and low memory utilization.
 * Java 1.5+

Licensing
The OWASP HTML Sanitizer is free to use and is dual licensed under the Apache 2 License and the New BSD License.


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What is this?
The OWASP HTML Sanitizer Projects provides Java based HTML sanitization of untrusted HTML!

Code Repo
OWASP HTML Sanitizer at GitHub

Email List
Questions? Please sign up for our Project Support List

Project Leaders
Author/Project Leader Mike Samuel [mailto:mikesamuel@gmail.com @] Project Manager Jim Manico [mailto:jim.manico@owasp.org @]

Related Projects

 * XSS (Cross Site Scripting) Prevention Cheat Sheet
 * OWASP JSON Sanitizer
 * OWASP Java Encoder Project
 * OWASP Dependency Check
 * OWASP AntiSamy
 * Sourceclear Headlines
 * Google KeyCzar
 * Apache SHIRO

Ohloh

 * https://www.ohloh.net/p/owasp-java-html-sanitizer


 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download
v239 at Maven Central JavaDoc v239

News and Events

 * [1 May 2015] Move to GitHub
 * [2 July 2014] v239 Released
 * [3 Mar 2014] v226 Released
 * [5 Feb 2014] New Wiki
 * [4 Sept 2013] v209 Released

Change Log
For recent release notes, please visit the changelog on GitHub.

Classifications

 * }

= Creating a HTML Policy =

You can use prepackaged policies here: https://github.com/OWASP/java-html-sanitizer/blob/master/src/main/java/org/owasp/html/Sanitizers.java.

PolicyFactory policy = Sanitizers.FORMATTING.and(Sanitizers.LINKS); String safeHTML = policy.sanitize(untrustedHTML);

or the tests show how to configure your own policy here: https://github.com/OWASP/java-html-sanitizer/blob/master/src/test/java/org/owasp/html/HtmlPolicyBuilderTest.java

PolicyFactory policy = new HtmlPolicyBuilder .allowElements("a") .allowUrlProtocols("https") .allowAttributes("href").onElements("a") .requireRelNofollowOnLinks .build; String safeHTML = policy.sanitize(untrustedHTML);

... or you can write custom policies to do things like changing h1s to divs with a certain class ...

PolicyFactory policy = new HtmlPolicyBuilder .allowElements("p") .allowElements(       new ElementPolicy {          public String apply(String elementName, List attrs) {            attrs.add("class");            attrs.add("header-" + elementName);            return "div";          }        }, "h1", "h2", "h3", "h4", "h5", "h6"))    .build; String safeHTML = policy.sanitize(untrustedHTML);

You can also use the default "ebay" and "slashdot" policies. The Slashdot policy (defined here https://github.com/OWASP/java-html-sanitizer/blob/master/src/main/java/org/owasp/html/examples/SlashdotPolicyExample.java) allows the following tags ("a", "p", "div", "i", "b", "em", "blockquote", "tt", "strong"n "br", "ul", "ol", "li") and only certain attributes. This policy also allows for the custom slashdot tags, "quote" and "ecode".

= Questions =

How was this project tested? This code was written with security best practices in mind, has an extensive test suite, and has undergone adversarial security review.

How is this project deployed? This project is best deployed through Maven https://github.com/OWASP/java-html-sanitizer/blob/master/docs/getting_started.md