Merge branch '434146-update-dast-check-docs' into 'master'

Update Documentation for Available Active Checks

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/139068



Merged-by: Russell Dickenson <rdickenson@gitlab.com>
Approved-by: Russell Dickenson <rdickenson@gitlab.com>
Co-authored-by: Arpit Gogia <12347103-arpitgogia@users.noreply.gitlab.com>

doc/user/application_security/dast/checks/319.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Mixed Content

doc/user/application_security/dast/checks/352.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Absence of anti-CSRF tokens

doc/user/application_security/dast/checks/359.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of Private Personal Information (PII) to an unauthorized actor (credit card)

doc/user/application_security/dast/checks/359.2.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of Private Personal Information (PII) to an unauthorized actor (United States social security number)

doc/user/application_security/dast/checks/548.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of information through directory listing

doc/user/application_security/dast/checks/598.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Use of GET request method with sensitive query strings (session ID)

doc/user/application_security/dast/checks/598.2.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Use of GET request method with sensitive query strings (password)

doc/user/application_security/dast/checks/598.3.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Use of GET request method with sensitive query strings (Authorization header details)

doc/user/application_security/dast/checks/601.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # URL redirection to untrusted site ('open redirect')

doc/user/application_security/dast/checks/611.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # External XML Entity Injection (XXE)

doc/user/application_security/dast/checks/614.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Sensitive cookie without Secure attribute

doc/user/application_security/dast/checks/693.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Missing X-Content-Type-Options: nosniff

doc/user/application_security/dast/checks/74.1.md

+---
+stage: Secure
+group: Dynamic Analysis
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
+---
+
+# XSLT Injection
+
+## Description
+
+It is possible to supply an XSL template to a server-side XSLT processor. XSLT processors can
+be abused to read or write files, initiate outbound connections, and in some cases execute
+arbitrary code.
+
+## Remediation
+
+Applications should never accept user-supplied style sheets. XSLT processors are not built to
+handle potentially malicious stylesheet files. However, some processors do implement or offer
+security features which may be available. Consult the documentation for the XSLT processor
+used by the target application for security guidelines and hardening steps. It is recommended
+that all XML parsers and processors at the very least disable external entity resolution.
+
+## Details
+
+| ID | Aggregated | CWE | Type | Risk |
+|:---|:--------|:--------|:--------|:--------|
+| 74.1 | false | 74 | Active | high |
+
+## Links
+
+- [CWE](https://cwe.mitre.org/data/definitions/74.html)

doc/user/application_security/dast/checks/78.1.md

+---
+stage: Secure
+group: Dynamic Analysis
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
+---
+
+# OS Command Injection
+
+## Description
+
+It is possible to execute arbitrary OS commands on the target application server.
+OS Command Injection is a critical vulnerability that can lead to a full system
+compromise.
+
+## Remediation
+
+User input should never be used in constructing commands or command arguments
+to functions which execute OS commands. This includes filenames supplied by
+user uploads or downloads.
+
+Ensure your application does not:
+
+- Use user-supplied information in the process name to execute.
+- Use user-supplied information in an OS command execution function which does
+not escape shell meta-characters.
+- Use user-supplied information in arguments to OS commands.
+
+The application should have a hardcoded set of arguments that are to be passed
+to OS commands. If file names are being passed to these functions, it is
+recommended that a hash of the file name be used instead, or some other unique
+identifier. It is strongly recommended that a native library that implements
+the same functionality be used instead of using OS system commands due to the
+risk of unknown attacks against third party commands.
+
+## Details
+
+| ID | Aggregated | CWE | Type | Risk |
+|:---|:--------|:--------|:--------|:--------|
+| 78.1 | false | 78 | Active | high |
+
+## Links
+
+- [OWASP](https://owasp.org/www-community/attacks/Command_Injection)
+- [CWE](https://cwe.mitre.org/data/definitions/78.html)

doc/user/application_security/dast/checks/798.1.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of confidential secret or token Adafruit API Key

doc/user/application_security/dast/checks/798.10.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of confidential secret or token Asana Client Secret

doc/user/application_security/dast/checks/798.100.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of confidential secret or token Sendbird Access Token

doc/user/application_security/dast/checks/798.101.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of confidential secret or token SendGrid API token

doc/user/application_security/dast/checks/798.102.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of confidential secret or token Sendinblue API token

doc/user/application_security/dast/checks/798.103.md

 ---
 stage: Secure
 group: Dynamic Analysis
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Exposure of confidential secret or token Sentry Access Token