From 29f0c0607ad3d25491f4c4a6ca19b463610ae92d Mon Sep 17 00:00:00 2001
From: René Kijewski <kijewski@library.vetmed.fu-berlin.de>
Date: Tue, 1 Feb 2022 15:32:37 +0100
Subject: Make json filter safe

Previously the built-in json filter had an issue that made it unsafe to
use in HTML data. When used in HTML attributes an attacker who is able
to supply an arbitrary string that should be JSON encoded could close
the containing HTML element e.g. with `"</div>"`, and write arbitrary
HTML code afterwards as long as they use apostrophes instead of
quotation marks. The programmer could make this use case safe by
explicitly escaping the JSON result: `{{data|json|escape}}`.

In a `<script>` context the json filter was not usable at all, because
in scripts HTML escaped entities are not parsed outside of XHTML
documents. Without using the safe filter an attacker could close the
current script using `"</script>"`.

This PR fixes the problem by always escaping less-than, greater-than,
ampersand, and apostrophe characters using their JSON unicode escape
sequence `\u00xx`. Unless the programmer explicitly uses the safe
filter, quotation marks are HTML encoded as `&quot`. In scripts the
programmer should use the safe filter, otherwise not.
---
 askama_escape/Cargo.toml | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'askama_escape/Cargo.toml')

diff --git a/askama_escape/Cargo.toml b/askama_escape/Cargo.toml
index ed7148c..643f81a 100644
--- a/askama_escape/Cargo.toml
+++ b/askama_escape/Cargo.toml
@@ -17,6 +17,9 @@ maintenance = { status = "actively-developed" }
 [dev-dependencies]
 criterion = "0.3"
 
+[features]
+json = []
+
 [[bench]]
 name = "all"
 harness = false
-- 
cgit