Given JSON-like content, The JSON Sanitizer converts it to valid JSON.
This can be attached at either end of a data-pipeline to help satisfy Postel's principle:
be conservative in what you do, be liberal in what you accept from others
Applied to JSON-like content from others, it will produce well-formed JSON that should satisfy any parser you use.
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.
Many applications have large amounts of code that uses ad-hoc methods to generate JSON outputs.
Frequently these outputs all pass through a small amount of framework
code before being sent over the network. This small amount of
framework code can use this library to make sure that the ad-hoc
outputs are standards compliant and safe to pass to (overly) powerful
Applications also often have web service APIs that receive JSON from a variety of sources. When this JSON is created using ad-hoc methods, this library can massage it into a form that is easy to parse.
By hooking this library into the code that sends and receives requests and responses, this library can help software architects ensure system-wide security and well-formedness guarantees.
The sanitizer takes JSON like content, and interprets it as JS eval would. Specifically, it deals with these non-standard constructs.
||Single quoted strings are converted to JSON strings.|
||Hex escapes are converted to JSON unicode escapes.|
||Octal escapes are converted to JSON unicode escapes.|
||Hex integer literals are converted to JSON decimal numbers.|
||Octal integer literals are converted to JSON decimal numbers.|
||Decimal numbers are coerced to JSON's stricter format.|
||Elisions in arrays are filled with
||Trailing commas are removed.|
||Unquoted property names are quoted.|
||JS style line and block comments are removed.|
||Grouping parentheses are removed.|
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 these additional properties:
- The output will not contain the substring (case-insensitively)
"</script"so can be embedded inside an HTML script element without further encoding.
- The output will not contain the substring
"]]>"so can be embedded inside an XML CDATA section without further encoding.
evalbuiltin (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).
- 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
have no side-effects and no free variables, so is neither a code-injection
vector, nor a vector for exfiltration of secrets.
phase has no side effects and resolves no free variables, and cannot
control how other client side code later interprets the resulting
data that is controlled by an attacker and passes it back through a
powerful interpreter like
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 of the input in UTF-16 code-units.