From cffec3edff2addc6d8b0d714fed1ae5d66e4876f Mon Sep 17 00:00:00 2001 From: "xuanyi.wang" Date: Thu, 25 May 2023 17:47:10 +0200 Subject: [PATCH] Update page 'OWASP test - Sloetjes' --- OWASP test - Sloetjes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OWASP test - Sloetjes.md b/OWASP test - Sloetjes.md index 7489093..96f9932 100644 --- a/OWASP test - Sloetjes.md +++ b/OWASP test - Sloetjes.md @@ -139,7 +139,7 @@ > In UTF-7, the left angle bracket (<) can be represented as "+ADw-". Note that this can contribute to XSS vulnerabilities if a web application's content-type can be changed or the charset is not specified and the browser interprets the charset as UTF-7. * List three things to look for in an input sanitizer to avoid XSS problems. -> * Input sanitizers should: +> Input sanitizers should: > * Be context-aware: Different contexts (like HTML, URLs, CSS, or JavaScript) have different rules about what characters are dangerous. > * Encode or remove special characters: Characters like <, >, ", ', and & often need to be encoded depending on context. > * Be regularly updated and maintained: New attack techniques are discovered regularly, and a good sanitizer library will keep up with these techniques. \ No newline at end of file