|Name ||Cross-Site Scripting via Encoded URI Schemes |
|Solutions ||Design: Use browser technologies that do not allow client side scripting.
Design: Utilize strict type, character, and encoding enforcement.
Implementation: Ensure all content that is delivered to client is sanitized against an acceptable content specification.
Implementation: Ensure all content coming from the client is using the same encoding; if not, the server-side application must canonicalize the data before applying any filtering.
Implementation: Perform input validation for all remote content, including remote and user-generated content
Implementation: Perform output validation for all remote content.
Implementation: Patching software. There are many attack vectors for XSS on the client side and the server side. Many vulnerabilities are fixed in service packs for browser, web servers, and plug in technologies, staying current on patch release that deal with XSS countermeasures mitigates this. |
|CWE ID ||Description |
|CWE-20 ||Improper Input Validation |
|CWE-71 ||Apple '.DS_Store' |
|CWE-79 ||Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
|CWE-84 ||Improper Neutralization of Encoded URI Schemes in a Web Page |
|CWE-85 ||Doubled Character XSS Manipulations |
|CWE-86 ||Improper Neutralization of Invalid Characters in Identifiers in Web Pages |
|CWE-692 || |
|CWE-697 ||Insufficient Comparison |
|CWE-713 || |