XSS Reorganization - Githubissues

manindar-mohan commented 1 year ago

This PR fixes #591.

[x] This PR handles the issue and requires no additional PRs.
[x] You have validated the need for this change.

What did this PR accomplish?

Moved all XSS to chapter 11, client-side testing
added sub-sections for XSS

Thank you for your contribution!

github-actions[bot] commented 1 year ago

The following issues were identified: document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:22 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "triple-backtickjs"] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:24 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "triple-backtick"] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:29 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "triple-backtick"] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:30:167 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:59:102 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:60 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "triple-backtickjs"] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:66:131 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:74:234 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:75 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "triple-backtickjs"] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md:81:93 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.3-Testing_for_DOM-based_Cross_Site_Scripting.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "cheatsheetseries.owasp.org/che..."] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.3-Testing_for_DOM-based_Cross_Site_Scripting.md:6 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- [DOM XSS article by Amit Kle..."] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.3-Testing_for_DOM-based_Cross_Site_Scripting.md:7 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "# Testing for DOM-Based Cross Site Scripting"] document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.3-Testing_for_DOM-based_Cross_Site_Scripting.md:96:94 MD047/single-trailing-newline Files should end with a single newline character

github-actions[bot] commented 1 year ago

The following links are broken: FILE:document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/03-Testing_for_SQL_Injection.md [✖] 05.1-Testing_for_Oracle.md → Status: 400 [✖] 05.2-Testing_for_MySQL.md → Status: 400 [✖] 05.3-Testing_for_SQL_Server.md → Status: 400 [✖] 05.4-Testing_PostgreSQL.md → Status: 400 [✖] 05.5-Testing_for_MS_Access.md → Status: 400 [✖] 05.6-Testing_for_NoSQL_Injection.md → Status: 400 [✖] 05.7-Testing_for_ORM_Injection.md → Status: 400 [✖] 05.8-Testing_for_Client-side.md → Status: 400

github-actions[bot] commented 1 year ago

The following mistakes were identified:

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/02-Testing_for_HTTP_Parameter_Pollution.md 23:720 ✖ Incorrect usage of the term: “web site”, use “site” instead terminology 57:5 ✖ Incorrect usage of the term: “node.js”, use “Node.js” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/03.1-Testing_for_Oracle.md 109:37 ✖ Incorrect usage of the term: “webpage”, use “web page” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/03.2-Testing_for_MySQL.md 63:66 ✖ Incorrect usage of the term: “back end”, use “backend” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/06-Testing_for_SSI_Injection.md 75:9 ✖ Incorrect usage of the term: “Server Side”, use “server-side” instead terminology 76:37 ✖ Incorrect usage of the term: “Server Side”, use “server-side” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/08-Testing_for_IMAP_SMTP_Injection.md 11:104 ✖ Incorrect usage of the term: “Internet”, use “internet” instead terminology 13:124 ✖ Incorrect usage of the term: “Internet”, use “internet” instead terminology 13:263 ✖ Incorrect usage of the term: “front-end”, use “frontend” instead terminology 18:231 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology 40:450 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/09.1-Testing_for_File_Inclusion.md 88:203 ✖ Incorrect usage of the term: “website”, use “site” instead terminology 94:112 ✖ Incorrect usage of the term: “website”, use “site” instead terminology 101:149 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology 103:80 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/10-Testing_for_Command_Injection.md 39:99 ✖ Incorrect usage of the term: “Internet”, use “internet” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/12-Testing_for_Format_String_Injection.md 85:8 ✖ Incorrect usage of the term: “web site”, use “site” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/13-Testing_for_Incubated_Vulnerability.md 25:75 ✖ Incorrect usage of the term: “web site”, use “site” instead terminology 54:402 ✖ Incorrect usage of the term: “web site”, use “site” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/14-Testing_for_HTTP_Splitting_Smuggling.md 63:492 ✖ Incorrect usage of the term: “Internet”, use “internet” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/16-Testing_for_Host_Header_Injection.md 119:115 ✖ Incorrect usage of the term: “website”, use “site” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/17-Testing_for_Server-side_Template_Injection.md 123:4 ✖ Incorrect usage of the term: “Server Side”, use “Server-side” instead terminology 125:34 ✖ Incorrect usage of the term: “server side”, use “server-side” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/18-Testing_for_Server-Side_Request_Forgery.md 19:321 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology 19:386 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology 97:178 ✖ Incorrect usage of the term: “Server Side”, use “Server-side” instead terminology 104:10 ✖ Incorrect usage of the term: “Server Side”, use “server-side” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/19-Testing_for_Mass_Assignment.md 97:39 ✖ Incorrect usage of the term: “back end”, use “backend” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/11-Client-side_Testing/01-Testing_for_Cross_Site_Scripting.md 103:128 ✖ Incorrect usage of the term: “whitelist”, use “allow list(s), or re-write as applicable” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.1-Testing_for_Reflected_Cross_Site_Scripting.md 164:21 ✖ Incorrect usage of the term: “white space”, use “whitespace” instead terminology 174:189 ✖ Incorrect usage of the term: “web site”, use “site” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.2-Testing_for_Stored_Cross_Site_Scripting.md 7:271 ✖ Incorrect usage of the term: “web site”, use “site” instead terminology 42:78 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology 158:159 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology 160:7 ✖ Incorrect usage of the term: “front-end”, use “frontend” instead terminology 163:10 ✖ Incorrect usage of the term: “back-end”, use “backend” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.3-Testing_for_DOM-based_Cross_Site_Scripting.md 40:186 ✖ Incorrect usage of the term: “website”, use “site” instead terminology 40:326 ✖ Incorrect usage of the term: “websites”, use “sites” instead terminology 1:77 ✖ Incorrect usage of the term: “html”, use “HTML” instead terminology

/home/runner/work/wstg/wstg/document/4-Web_Application_Security_Testing/11-Client-side_Testing/01.4-Testing_for_Self_DOM_Based_Cross_Site_Scripting.md 22:69 ✖ Incorrect usage of the term: “website”, use “site” instead terminology