-
Notifications
You must be signed in to change notification settings - Fork 112
Home
The OWASP Java Encoder provides:
- Output Encoding functions to help stop XSS
- Java 1.5+ standalone library
The OWASP Java Encoder is a Java 1.5+ simple-to-use drop-in high-performance encoder class with no dependencies and little baggage. This project will help Java web developers defend against Cross Site Scripting!
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts (primarily JavaScript) are injected into otherwise trusted web sites. You can read more about Cross Site Scripting here: Cross-site_Scripting_%28XSS%29. One of the primary defenses to stop Cross Site Scripting is a technique called Contextual Output Encoding. You can read more about Cross Site Scripting prevention here: XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet.
Contextual Output Encoding is a computer programming technique necessary to stop Cross Site Scripting. This project is a Java 1.5+ simple-to-use drop-in high-performance encoder class with no dependencies and little baggage. It provides numerous encoding functions to help defend against XSS in a variety of different HTML, JavaScript, XML and CSS contexts.
The OWASP Java Encoder library is intended for quick contextual encoding with very little overhead, either in performance or usage. To get started, simply add the encoder-1.1.1.jar, import org.owasp.encoder.Encode and start encoding.
Please look at the javadoc for Encode to see the variety of contexts for which you can encode. Tag libraries and JSP EL functions can be found in the encoder-jsp-1.1.1.jar.
The OWASP Java Encoder is free to use under the New BSD License.
Lead Author: Jeff Ichnowski jeff.ichnowski@gmail.com
Jim Manico jim.manico@owasp.org
Jeremy Long jeremy.long@owasp.org
- [Apr] Moved to GitHub
- [Feb] Removed ThreadLocal use from trunk
- [20] Doc additions
- [5] New Wiki
- [4] 1.1.1 Released
The OWASP Java Encoder version 1.1.1 is now available in central!
OWASP Encoder at Maven Central.
Direct Download: encoder-1.1.1.jar
<dependency>
<groupId>org.owasp.encoder</groupid>
<artifactId>encoder</artifactid>
<version>1.1.1</version>
</dependency>
Direct Download: encoder-jsp-1.1.1.jar
<dependency>
<groupId>org.owasp.encoder</groupid>
<artifactId>encoder-jsp</artifactid>
<version>1.1.1</version>
</dependency>
The following describes the Grave Accent XSS issue with unpatched versions of Internet Explorer. Thank you to Rafay Baloch for bringing this to our attention and to Jeff Ichnowski for the workaround.
The grave accent (`), ASCII 96, hex 60 (wikipedia) is subject to a critical flaw in unpatched Internet Explorer. There is no possible encoding of the character that can avoid the issue. For a more in depth presentation on the issue discussed herein, please see Mario Heidrech's presentation.
In Internet Explorer, the grave accent is usable as an HTML attribute quotation character, equivalent to single and double quotes. Specifically, IE treats the following as equivalent:
<body><b><%= Encode.forHtml(textValue) %>" /></b></body>
<input value="this is the value"> <input value=`this is the value`>
It is an IE extension, is not in HTML specifications (HTML4, HTML5), and is probably not well supported in other browsers.
The following HTML snippet, demonstrates the cross-site scripting vulnerability related to grave accents on unpatched Internet Explorer:
<div id=a><input value="``onmouseover=alert(1)"></div> <div id=b></div> <script>b.innerHTML=a.innerHTML</script>
When this snippet is run in Internet Explorer the following steps happen:
- Two div elements are created with id's "a" and "b"
- The script executes "a.innerHTML" which returns:
<input value=``onmouseover=alert(1)>
- The script sets "b.innerHTML" to the value from (2) and is converted to the DOM equivalent of
<input value="" onmouseover="alert(1)">
The XSS issue arises from IE returning a value from innerHTML that it does not parse back into the original DOM. Patched version of IE fix this issue by returning the XSS value as a double-quoted attribute. The issue is complicated by the fact that no possible encoding of the grave accent can avoid this issue.
When...
<input value="``onmouseover=alert(1)">
...is the input, "a.innerHTML" returns the same XSS vector as it does without the encoding.
Our recommended workaround is to update any JavaScript based innerHTML read to replace the accent grave with a numeric entity encoded form: "`". As an example, the following change to the XSS vulnerable code above fixes the issue:
<script>a.innerHTML=b.innerHTML.replace(/`/g, "`");</script>
This can be done in any library code that reads the innerHTML. To follow how this addresses the issue, the innerHTML from step 2 of the issue is converted to:
<input value=&#96;&#96;onmouseover=alert(1)>
Since the browser will no longer see the grave accents as an empty attribute, it will convert the input back to a copy of its original DOM.
As there is no encoding option available, the following options are available to web application authors:
- Do not use innerHTML copies
- Filter out the accent grave from any user input
- Clean up grave accents when using an innerHTML copy
The OWASP Java Encoder Library at its core is intended to be a XSS safe _encoding_ library. The grave accent is a legitimate and frequently used character, that cannot be encoded to avoid this bug in unpatched versions of IE. With enough user feedback, we may update the library to include one of the following options: (1) alternate, drop-in build that filters grave accents, with unchanged API, (2) new filtering methods.