5.3 Output encoding and Injection Prevention Requirements¶
Browse by item:
- 5.3.1 Output encoding is relevant for the interpreter and context required
- 5.3.2 Output encoding preserves the user’s chosen character set and locale
- 5.3.3 Context-aware output escaping protects against reflected, stored, and DOM based XSS
- 5.3.4 Data selection or database queries are protected against database injection attacks
- 5.3.5 Context-specific output encoding is used where parameterized or safer mechanisms are not present
- 5.3.6 The application protects against JavaScript or JSON injection attacks
- 5.3.7 The application protects against LDAP injection vulnerabilities
- 5.3.8 The application protects against OS command injection
- 5.3.9 The application protects against Local File Inclusion (LFI)
- 5.3.10 The application protects against XPath injection or XML injection attacks