Difference between revisions of "OWASP JSON Sanitizer"

Importing the JSON Sanitizer

You can fetch the jars from Maven Central or you can let your favorite java package manager handle it for you via

   <dependency>
     <groupId>com.mikesamuel</groupId>
     <artifactId>json-sanitizer</artifactId>
     <version>[1.0,)</version>
   </dependency>

Once you've got the JSON sanitizer JAR on your classpath,

   import com.google.json.JsonSanitizer;

will let you call

   String wellFormedJson = JsonSanitizer.sanitize(myJsonLikeString);

That's it. Now wellFormedJson is a string of well-formed JSON that is safe to pass to JavaScript?'s eval operator and which can be easily embedded in XML or HTML.

If you have further questions, check our support list.

The OWASP JSON Sanitizer Project is a simple to use Java library that can be attached at either end of a data-pipeline. When applied to JSON-like content from others, this project will produce well-formed JSON that should satisfy any parser you use. When applied to your output before you send, it will coerce minor mistakes in encoding and make it easier to embed your JSON in HTML and XML.

The sanitizer takes JSON like content, and interprets it as JS eval would. Specifically, it deals with these non-standard constructs.

The sanitizer fixes missing punctuation, end quotes, and mismatched or missing close brackets. If an input contains only white-space then the valid JSON string null is substituted.

The output is well-formed JSON as defined by RFC 4627. The output satisfies three additional properties:

1. The output will not contain the substring (case-insensitively) "</script" so can be embedded inside an HTML script element without further encoding.
2. The output will not contain the substring "]]>" so can be embedded inside an XML CDATA section without further encoding.
3. The output is a valid Javascript expression, so can be parsed by Javascript's eval builtin (after being wrapped in parentheses) or by JSON.parse. Specifically, the output will not contain any string literals with embedded JS newlines (U+2028 Paragraph separator or U+2029 Line separator).
4. The output contains only valid Unicode scalar values (no isolated UTF-16 surrogates) that are allowed in XML unescaped.

Since the output is well-formed JSON, passing it to eval will have no side-effects and no free variables, so is neither a code-injection vector, nor a vector for exfiltration of secrets.

This library only ensures that the JSON string → Javascript object phase has no side effects and resolves no free variables, and cannot control how other client side code later interprets the resulting Javascript object. So if client-side code takes a part of the parsed data that is controlled by an attacker and passes it back through a powerful interpreter like eval or innerHTML then that client-side code might suffer unintended side-effects.

  var myValue = eval(sanitizedJsonString);  // safe
  var myEmbeddedValue = eval(myValue.foo);  // possibly unsafe

Additionally, sanitizing JSON cannot protect an application from Confused Deputy attacks

  var myValue = JSON.parse(sanitizedJsonString);
  addToAdminstratorsGroup(myValue.propertyFromUntrustedSource);

The sanitize method will return the input string without allocating a new buffer when the input is already valid JSON that satisfies the properties above. Thus, if used on input that is usually well formed, it has minimal memory overhead.

The sanitize method takes O(n) time where n is the length in UTF-16 code-units.

The JSON Sanitizer is similar to a decoupling capacitor.

Any module that takes noisy input in and puts out clean output helps *decouple* the security properties of one piece of code (that uses eval) from the security properties of another (that concatenates untrusted strings to produce JSON) so that a failure in one does not necessitate a failure in the other.