url
stringlengths 24
122
| repo_url
stringlengths 60
156
| date_extracted
stringdate 2025-08-13 00:00:00
2025-08-13 00:00:00
| root
stringlengths 3
85
| breadcrumbs
listlengths 1
6
| filename
stringlengths 6
60
| stage
stringclasses 33
values | group
stringclasses 81
values | info
stringclasses 22
values | title
stringlengths 3
110
⌀ | description
stringlengths 11
359
⌀ | clean_text
stringlengths 47
3.32M
| rich_text
stringlengths 321
3.32M
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://docs.gitlab.com/user/application_security
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/_index.md
|
2025-08-13
|
doc/user/application_security
|
[
"doc",
"user",
"application_security"
] |
_index.md
|
Application Security Testing
|
Static Analysis
|
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
|
Application security testing
|
Scanning, vulnerabilities, compliance, customization, and reporting.
|
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Build security into your development process with GitLab application security testing capabilities.
These features help you identify and address vulnerabilities early in your development lifecycle,
before they reach production environments.
GitLab application security testing provides comprehensive coverage of both repository content and
deployed applications, enabling you to detect potential security issues throughout your software
development lifecycle.
GitLab also helps reduce the risk of vulnerabilities being introduced through several protective
mechanisms:
Secret push protection
: Blocks secrets such as keys and API tokens from being pushed to GitLab.
Merge request approval policies
: Enforce an additional approval on merge requests that would introduce vulnerabilities.
For a click-through demo, see [Integrating security to the pipeline](https://gitlab.navattic.com/gitlab-scans).
<!-- Demo published on 2024-01-15 -->
## How application security testing works
GitLab detects security vulnerabilities throughout your code, dependencies, containers, and
deployed applications. Your project's repository and your application's behavior are scanned for
vulnerabilities.
Security findings appear directly in merge requests, providing actionable information before code is
merged. This proactive approach reduces the cost and effort of fixing issues later in development.
Application security testing can run in several contexts:
During development
: Automated scans run as part of CI/CD pipelines when code is committed or merge requests are
created.
Outside development
: Security testing can be run manually on demand or scheduled to run at regular intervals.
## Vulnerability management lifecycle
GitLab assists in the complete vulnerability management lifecycle through key phases:
[Detect](detect/_index.md)
: Identify vulnerabilities through automated scanning and security testing.
[Triage](triage/_index.md)
: Evaluate and prioritize vulnerabilities to determine which need immediate attention and which
can be addressed later.
[Analyze](analyze/_index.md)
: Conduct detailed analysis of confirmed vulnerabilities to understand their impact and determine
appropriate remediation strategies.
[Remediate](remediate/_index.md)
: Fix the root cause of vulnerabilities or implement appropriate risk mitigation measures.
Vulnerabilities are centralized in the vulnerability report and security dashboard, making
prioritization and remediation tracking more straightforward for security teams.
## Get started
To get started, see [Get started securing your application](get-started-security.md).
|
---
stage: Application Security Testing
group: Static 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
title: Application security testing
description: Scanning, vulnerabilities, compliance, customization, and reporting.
breadcrumbs:
- doc
- user
- application_security
---
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Build security into your development process with GitLab application security testing capabilities.
These features help you identify and address vulnerabilities early in your development lifecycle,
before they reach production environments.
GitLab application security testing provides comprehensive coverage of both repository content and
deployed applications, enabling you to detect potential security issues throughout your software
development lifecycle.
GitLab also helps reduce the risk of vulnerabilities being introduced through several protective
mechanisms:
Secret push protection
: Blocks secrets such as keys and API tokens from being pushed to GitLab.
Merge request approval policies
: Enforce an additional approval on merge requests that would introduce vulnerabilities.
For a click-through demo, see [Integrating security to the pipeline](https://gitlab.navattic.com/gitlab-scans).
<!-- Demo published on 2024-01-15 -->
## How application security testing works
GitLab detects security vulnerabilities throughout your code, dependencies, containers, and
deployed applications. Your project's repository and your application's behavior are scanned for
vulnerabilities.
Security findings appear directly in merge requests, providing actionable information before code is
merged. This proactive approach reduces the cost and effort of fixing issues later in development.
Application security testing can run in several contexts:
During development
: Automated scans run as part of CI/CD pipelines when code is committed or merge requests are
created.
Outside development
: Security testing can be run manually on demand or scheduled to run at regular intervals.
## Vulnerability management lifecycle
GitLab assists in the complete vulnerability management lifecycle through key phases:
[Detect](detect/_index.md)
: Identify vulnerabilities through automated scanning and security testing.
[Triage](triage/_index.md)
: Evaluate and prioritize vulnerabilities to determine which need immediate attention and which
can be addressed later.
[Analyze](analyze/_index.md)
: Conduct detailed analysis of confirmed vulnerabilities to understand their impact and determine
appropriate remediation strategies.
[Remediate](remediate/_index.md)
: Fix the root cause of vulnerabilities or implement appropriate risk mitigation measures.
Vulnerabilities are centralized in the vulnerability report and security dashboard, making
prioritization and remediation tracking more straightforward for security teams.
## Get started
To get started, see [Get started securing your application](get-started-security.md).
|
https://docs.gitlab.com/user/secure_your_application
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/secure_your_application.md
|
2025-08-13
|
doc/user/application_security
|
[
"doc",
"user",
"application_security"
] |
secure_your_application.md
|
Application Security Testing
|
Static Analysis
|
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
|
Secure your application
|
Container, dependency, and vulnerability scans.
|
GitLab can check your applications for security vulnerabilities.
{{< cards >}}
- [Getting started](get-started-security.md)
- [Tutorials](../../tutorials/secure_application.md)
- [Application security](_index.md)
- [Compliance](../compliance/_index.md)
- [Detect](detect/_index.md)
- [Triage](triage/_index.md)
- [Analyze](analyze/_index.md)
- [Remediate](remediate/_index.md)
- [GitLab Advisory Database](gitlab_advisory_database/_index.md)
- [CVE ID requests](cve_id_request.md)
- [Policies](policies/_index.md)
- [Security glossary](terminology/_index.md)
{{< /cards >}}
|
---
stage: Application Security Testing
group: Static 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
description: Container, dependency, and vulnerability scans.
title: Secure your application
breadcrumbs:
- doc
- user
- application_security
---
GitLab can check your applications for security vulnerabilities.
{{< cards >}}
- [Getting started](get-started-security.md)
- [Tutorials](../../tutorials/secure_application.md)
- [Application security](_index.md)
- [Compliance](../compliance/_index.md)
- [Detect](detect/_index.md)
- [Triage](triage/_index.md)
- [Analyze](analyze/_index.md)
- [Remediate](remediate/_index.md)
- [GitLab Advisory Database](gitlab_advisory_database/_index.md)
- [CVE ID requests](cve_id_request.md)
- [Policies](policies/_index.md)
- [Security glossary](terminology/_index.md)
{{< /cards >}}
|
https://docs.gitlab.com/user/cve_id_request
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/cve_id_request.md
|
2025-08-13
|
doc/user/application_security
|
[
"doc",
"user",
"application_security"
] |
cve_id_request.md
|
Security Risk Management
|
Security Insights
|
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
|
CVE ID request
|
Vulnerability tracking and security disclosure.
|
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com
{{< /details >}}
For any public project, you can request a CVE identifier (ID).
A [CVE](https://cve.mitre.org/index.html) identifier is assigned to a publicly-disclosed software
vulnerability. GitLab is a [CVE Numbering Authority](https://about.gitlab.com/security/cve/)
([CNA](https://cve.mitre.org/cve/cna.html)).
Assigning a CVE ID to a vulnerability in your project helps your users stay secure and informed. For
example, [dependency scanning tools](dependency_scanning/_index.md) can
detect when vulnerable versions of your project are used as a dependency.
A common vulnerability workflow is:
1. Request a CVE for a vulnerability.
1. Reference the assigned CVE identifier in release notes.
1. Publish the vulnerability's details after the fix is released.
## Prerequisites
To [submit a CVE ID Request](#submit-a-cve-id-request) the following prerequisites must be met:
- The project is hosted on GitLab.com.
- The project is public.
- You are a maintainer of the project.
- The vulnerability's issue is [confidential](../project/issues/confidential_issues.md).
## Submit a CVE ID request
To submit a CVE ID request:
1. Go to the vulnerability's issue and select **Create CVE ID Request**. The new issue page of
the [GitLab CVE project](https://gitlab.com/gitlab-org/cves) opens.
1. In the **Title** box, enter a brief description of the vulnerability.
1. In the **Description** box, enter the following details:
- A detailed description of the vulnerability
- The project's vendor and name
- Impacted versions
- Fixed versions
- The vulnerability class (a [CWE](https://cwe.mitre.org/data/index.html) identifier)
- A [CVSS v3 vector](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator)
GitLab updates your CVE ID request issue when:
- Your submission is assigned a CVE.
- Your CVE is published.
- MITRE is notified that your CVE is published.
- MITRE has added your CVE in the NVD feed.
## CVE assignment
After a CVE identifier is assigned, you can reference it as required. Details of the vulnerability
submitted in the CVE ID request are published according to your schedule.
|
---
stage: Security Risk Management
group: Security Insights
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
title: CVE ID request
description: Vulnerability tracking and security disclosure.
breadcrumbs:
- doc
- user
- application_security
---
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com
{{< /details >}}
For any public project, you can request a CVE identifier (ID).
A [CVE](https://cve.mitre.org/index.html) identifier is assigned to a publicly-disclosed software
vulnerability. GitLab is a [CVE Numbering Authority](https://about.gitlab.com/security/cve/)
([CNA](https://cve.mitre.org/cve/cna.html)).
Assigning a CVE ID to a vulnerability in your project helps your users stay secure and informed. For
example, [dependency scanning tools](dependency_scanning/_index.md) can
detect when vulnerable versions of your project are used as a dependency.
A common vulnerability workflow is:
1. Request a CVE for a vulnerability.
1. Reference the assigned CVE identifier in release notes.
1. Publish the vulnerability's details after the fix is released.
## Prerequisites
To [submit a CVE ID Request](#submit-a-cve-id-request) the following prerequisites must be met:
- The project is hosted on GitLab.com.
- The project is public.
- You are a maintainer of the project.
- The vulnerability's issue is [confidential](../project/issues/confidential_issues.md).
## Submit a CVE ID request
To submit a CVE ID request:
1. Go to the vulnerability's issue and select **Create CVE ID Request**. The new issue page of
the [GitLab CVE project](https://gitlab.com/gitlab-org/cves) opens.
1. In the **Title** box, enter a brief description of the vulnerability.
1. In the **Description** box, enter the following details:
- A detailed description of the vulnerability
- The project's vendor and name
- Impacted versions
- Fixed versions
- The vulnerability class (a [CWE](https://cwe.mitre.org/data/index.html) identifier)
- A [CVSS v3 vector](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator)
GitLab updates your CVE ID request issue when:
- Your submission is assigned a CVE.
- Your CVE is published.
- MITRE is notified that your CVE is published.
- MITRE has added your CVE in the NVD feed.
## CVE assignment
After a CVE identifier is assigned, you can reference it as required. Details of the vulnerability
submitted in the CVE ID request are published according to your schedule.
|
https://docs.gitlab.com/user/troubleshooting_application_security
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/troubleshooting_application_security.md
|
2025-08-13
|
doc/user/application_security
|
[
"doc",
"user",
"application_security"
] |
troubleshooting_application_security.md
|
Application Security Testing
|
Static Analysis
|
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
|
Troubleshooting application security
|
How to troubleshoot GitLab application security features, including how to get more detailed logging.
|
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
When working with application security features, you might encounter the following issues.
## Logging level
The verbosity of logs output by GitLab analyzers is determined by the `SECURE_LOG_LEVEL` environment
variable. Messages of this logging level or higher are output.
From highest to lowest severity, the logging levels are:
- `fatal`
- `error`
- `warn`
- `info` (default)
- `debug`
### Debug-level logging
{{< alert type="warning" >}}
Debug logging can be a serious security risk. The output may contain the content of
environment variables and other secrets available to the job. The output is uploaded
to the GitLab server and is visible in job logs.
{{< /alert >}}
To enable debug-level logging, add the following to your `.gitlab-ci.yml` file:
```yaml
variables:
SECURE_LOG_LEVEL: "debug"
```
This indicates to all GitLab analyzers that they are to output **all** messages. For more details,
see [logging level](#logging-level).
<!-- NOTE: The below subsection(`### Secure job failing with exit code 1`) documentation URL is referred in the [/gitlab-org/security-products/analyzers/command](https://gitlab.com/gitlab-org/security-products/analyzers/command/-/blob/main/command.go#L19) repository. If this section/subsection changes, ensure to update the corresponding URL in the mentioned repository.
-->
## Secure job failing with exit code 1
If a Secure job is failing and it's unclear why:
1. Enable [debug-level logging](#debug-level-logging).
1. Run the job.
1. Examine the job's output.
1. Remove the `debug` log level to return to the default `info` value.
## Outdated security reports
When a security report generated for a merge request becomes outdated, the merge request shows a
warning message in the security widget and prompts you to take an appropriate action.
This can happen in two scenarios:
- Your [source branch is behind the target branch](#source-branch-is-behind-the-target-branch).
- The [target branch security report is out of date](#target-branch-security-report-is-out-of-date).
### Source branch is behind the target branch
A security report can be out of date when the most recent common ancestor commit between the
target branch and the source branch is not the most recent commit on the target branch.
To fix this issue, rebase or merge to incorporate the changes from the target branch.
### Target branch security report is out of date
This can happen for many reasons, including failed jobs or new advisories. When the merge request
shows that a security report is out of date, you must run a new pipeline on the target branch.
Select **new pipeline** to run a new pipeline.
## Getting warning messages `… report.json: no matching files`
{{< alert type="warning" >}}
Debug logging can be a serious security risk. The output may contain the content of
environment variables and other secrets available to the job. The output is uploaded
to the GitLab server and visible in job logs.
{{< /alert >}}
This message is often followed by the [error `No files to upload`](../../ci/jobs/job_artifacts_troubleshooting.md#error-message-no-files-to-upload),
and preceded by other errors or warnings that indicate why the JSON report wasn't generated. Check
the entire job log for such messages. If you don't find these messages, retry the failed job after
setting `SECURE_LOG_LEVEL: "debug"` as a [custom CI/CD variable](../../ci/variables/_index.md#for-a-project).
This provides extra information to investigate further.
## Getting error message `sast job: config key may not be used with 'rules': only/except`
When [including](../../ci/yaml/_index.md#includetemplate) a `.gitlab-ci.yml` template
like [`SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml),
the following error may occur, depending on your GitLab CI/CD configuration:
```plaintext
Unable to create pipeline
jobs:sast config key may not be used with `rules`: only/except
```
This error appears when the included job's `rules` configuration has been [overridden](sast/_index.md#overriding-sast-jobs)
with [the deprecated `only` or `except` syntax.](../../ci/yaml/deprecated_keywords.md#only--except)
To fix this issue, you must either:
- [Transition your `only/except` syntax to `rules`](#transitioning-your-onlyexcept-syntax-to-rules).
- (Temporarily) [Pin your templates to the deprecated versions](#pin-your-templates-to-the-deprecated-versions)
For more information, see [Overriding SAST jobs](sast/_index.md#overriding-sast-jobs).
### Transitioning your `only/except` syntax to `rules`
When overriding the template to control job execution, previous instances of
[`only` or `except`](../../ci/yaml/deprecated_keywords.md#only--except) are no longer compatible
and must be transitioned to [the `rules` syntax](../../ci/yaml/_index.md#rules).
If your override is aimed at limiting jobs to only run on `main`, the previous syntax
would look similar to:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is only executed on main or merge requests
spotbugs-sast:
only:
refs:
- main
- merge_requests
```
To transition the previous configuration to the new `rules` syntax, the override
would be written as follows:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is only executed on main or merge requests
spotbugs-sast:
rules:
- if: $CI_COMMIT_BRANCH == "main"
- if: $CI_MERGE_REQUEST_ID
```
If your override is aimed at limiting jobs to only run on branches, not tags,
it would look similar to:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast:
except:
- tags
```
To transition to the new `rules` syntax, the override would be rewritten as:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast:
rules:
- if: $CI_COMMIT_TAG == null
```
For more information, see [`rules`](../../ci/yaml/_index.md#rules).
### Pin your templates to the deprecated versions
To ensure the latest support, we **strongly** recommend that you migrate to [`rules`](../../ci/yaml/_index.md#rules).
If you're unable to immediately update your CI configuration, there are several workarounds that
involve pinning to the previous template versions, for example:
```yaml
include:
remote: 'https://gitlab.com/gitlab-org/gitlab/-/raw/12-10-stable-ee/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml'
```
Additionally, we provide a dedicated project containing the versioned legacy templates.
This can be used for offline setups or for anyone wishing to use [Auto DevOps](../../topics/autodevops/_index.md).
Instructions are available in the [legacy template project](https://gitlab.com/gitlab-org/auto-devops-v12-10).
### Vulnerabilities are found, but the job succeeds. How can you have a pipeline fail instead?
In these circumstances, that the job succeeds is the default behavior. The job's status indicates
success or failure of the analyzer itself. Analyzer results are displayed in the
[job logs](../../ci/jobs/job_logs.md#expand-and-collapse-job-log-sections),
[merge request widget](detect/security_scanning_results.md), or
[security dashboard](security_dashboard/_index.md).
## Error: job `is used for configuration only, and its script should not be executed`
[Changes made in GitLab 13.4](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41260)
to the `Security/Dependency-Scanning.gitlab-ci.yml` and `Security/SAST.gitlab-ci.yml`
templates mean that if you enable the `sast` or `dependency_scanning` jobs by setting the `rules` attribute,
they fail with the error `(job) is used for configuration only, and its script should not be executed`.
The `sast` or `dependency_scanning` stanzas can be used to make changes to all SAST or Dependency Scanning,
such as changing `variables` or the `stage`, but they cannot be used to define shared `rules`.
There [is an issue open to improve extendability](https://gitlab.com/gitlab-org/gitlab/-/issues/218444).
You can upvote the issue to help with prioritization, and
[contributions are welcomed](https://about.gitlab.com/community/contribute/).
## Empty vulnerability report, Dependency List pages
If the pipeline has manual steps with a job that has the `allow_failure: false` option, and this job is not finished,
GitLab can't populate listed pages with the data from security reports.
In this case, [the vulnerability report](vulnerability_report/_index.md) and [the Dependency List](dependency_list/_index.md)
pages are empty.
These security pages can be populated by running the jobs from the manual step of the pipeline.
There is [an issue open to handle this scenario](https://gitlab.com/gitlab-org/gitlab/-/issues/346843).
You can upvote the issue to help with prioritization, and
[contributions are welcomed](https://about.gitlab.com/community/contribute/).
|
---
stage: Application Security Testing
group: Static 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
title: Troubleshooting application security
description: How to troubleshoot GitLab application security features, including how
to get more detailed logging.
breadcrumbs:
- doc
- user
- application_security
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
When working with application security features, you might encounter the following issues.
## Logging level
The verbosity of logs output by GitLab analyzers is determined by the `SECURE_LOG_LEVEL` environment
variable. Messages of this logging level or higher are output.
From highest to lowest severity, the logging levels are:
- `fatal`
- `error`
- `warn`
- `info` (default)
- `debug`
### Debug-level logging
{{< alert type="warning" >}}
Debug logging can be a serious security risk. The output may contain the content of
environment variables and other secrets available to the job. The output is uploaded
to the GitLab server and is visible in job logs.
{{< /alert >}}
To enable debug-level logging, add the following to your `.gitlab-ci.yml` file:
```yaml
variables:
SECURE_LOG_LEVEL: "debug"
```
This indicates to all GitLab analyzers that they are to output **all** messages. For more details,
see [logging level](#logging-level).
<!-- NOTE: The below subsection(`### Secure job failing with exit code 1`) documentation URL is referred in the [/gitlab-org/security-products/analyzers/command](https://gitlab.com/gitlab-org/security-products/analyzers/command/-/blob/main/command.go#L19) repository. If this section/subsection changes, ensure to update the corresponding URL in the mentioned repository.
-->
## Secure job failing with exit code 1
If a Secure job is failing and it's unclear why:
1. Enable [debug-level logging](#debug-level-logging).
1. Run the job.
1. Examine the job's output.
1. Remove the `debug` log level to return to the default `info` value.
## Outdated security reports
When a security report generated for a merge request becomes outdated, the merge request shows a
warning message in the security widget and prompts you to take an appropriate action.
This can happen in two scenarios:
- Your [source branch is behind the target branch](#source-branch-is-behind-the-target-branch).
- The [target branch security report is out of date](#target-branch-security-report-is-out-of-date).
### Source branch is behind the target branch
A security report can be out of date when the most recent common ancestor commit between the
target branch and the source branch is not the most recent commit on the target branch.
To fix this issue, rebase or merge to incorporate the changes from the target branch.
### Target branch security report is out of date
This can happen for many reasons, including failed jobs or new advisories. When the merge request
shows that a security report is out of date, you must run a new pipeline on the target branch.
Select **new pipeline** to run a new pipeline.
## Getting warning messages `… report.json: no matching files`
{{< alert type="warning" >}}
Debug logging can be a serious security risk. The output may contain the content of
environment variables and other secrets available to the job. The output is uploaded
to the GitLab server and visible in job logs.
{{< /alert >}}
This message is often followed by the [error `No files to upload`](../../ci/jobs/job_artifacts_troubleshooting.md#error-message-no-files-to-upload),
and preceded by other errors or warnings that indicate why the JSON report wasn't generated. Check
the entire job log for such messages. If you don't find these messages, retry the failed job after
setting `SECURE_LOG_LEVEL: "debug"` as a [custom CI/CD variable](../../ci/variables/_index.md#for-a-project).
This provides extra information to investigate further.
## Getting error message `sast job: config key may not be used with 'rules': only/except`
When [including](../../ci/yaml/_index.md#includetemplate) a `.gitlab-ci.yml` template
like [`SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml),
the following error may occur, depending on your GitLab CI/CD configuration:
```plaintext
Unable to create pipeline
jobs:sast config key may not be used with `rules`: only/except
```
This error appears when the included job's `rules` configuration has been [overridden](sast/_index.md#overriding-sast-jobs)
with [the deprecated `only` or `except` syntax.](../../ci/yaml/deprecated_keywords.md#only--except)
To fix this issue, you must either:
- [Transition your `only/except` syntax to `rules`](#transitioning-your-onlyexcept-syntax-to-rules).
- (Temporarily) [Pin your templates to the deprecated versions](#pin-your-templates-to-the-deprecated-versions)
For more information, see [Overriding SAST jobs](sast/_index.md#overriding-sast-jobs).
### Transitioning your `only/except` syntax to `rules`
When overriding the template to control job execution, previous instances of
[`only` or `except`](../../ci/yaml/deprecated_keywords.md#only--except) are no longer compatible
and must be transitioned to [the `rules` syntax](../../ci/yaml/_index.md#rules).
If your override is aimed at limiting jobs to only run on `main`, the previous syntax
would look similar to:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is only executed on main or merge requests
spotbugs-sast:
only:
refs:
- main
- merge_requests
```
To transition the previous configuration to the new `rules` syntax, the override
would be written as follows:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is only executed on main or merge requests
spotbugs-sast:
rules:
- if: $CI_COMMIT_BRANCH == "main"
- if: $CI_MERGE_REQUEST_ID
```
If your override is aimed at limiting jobs to only run on branches, not tags,
it would look similar to:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast:
except:
- tags
```
To transition to the new `rules` syntax, the override would be rewritten as:
```yaml
include:
- template: Jobs/SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast:
rules:
- if: $CI_COMMIT_TAG == null
```
For more information, see [`rules`](../../ci/yaml/_index.md#rules).
### Pin your templates to the deprecated versions
To ensure the latest support, we **strongly** recommend that you migrate to [`rules`](../../ci/yaml/_index.md#rules).
If you're unable to immediately update your CI configuration, there are several workarounds that
involve pinning to the previous template versions, for example:
```yaml
include:
remote: 'https://gitlab.com/gitlab-org/gitlab/-/raw/12-10-stable-ee/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml'
```
Additionally, we provide a dedicated project containing the versioned legacy templates.
This can be used for offline setups or for anyone wishing to use [Auto DevOps](../../topics/autodevops/_index.md).
Instructions are available in the [legacy template project](https://gitlab.com/gitlab-org/auto-devops-v12-10).
### Vulnerabilities are found, but the job succeeds. How can you have a pipeline fail instead?
In these circumstances, that the job succeeds is the default behavior. The job's status indicates
success or failure of the analyzer itself. Analyzer results are displayed in the
[job logs](../../ci/jobs/job_logs.md#expand-and-collapse-job-log-sections),
[merge request widget](detect/security_scanning_results.md), or
[security dashboard](security_dashboard/_index.md).
## Error: job `is used for configuration only, and its script should not be executed`
[Changes made in GitLab 13.4](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41260)
to the `Security/Dependency-Scanning.gitlab-ci.yml` and `Security/SAST.gitlab-ci.yml`
templates mean that if you enable the `sast` or `dependency_scanning` jobs by setting the `rules` attribute,
they fail with the error `(job) is used for configuration only, and its script should not be executed`.
The `sast` or `dependency_scanning` stanzas can be used to make changes to all SAST or Dependency Scanning,
such as changing `variables` or the `stage`, but they cannot be used to define shared `rules`.
There [is an issue open to improve extendability](https://gitlab.com/gitlab-org/gitlab/-/issues/218444).
You can upvote the issue to help with prioritization, and
[contributions are welcomed](https://about.gitlab.com/community/contribute/).
## Empty vulnerability report, Dependency List pages
If the pipeline has manual steps with a job that has the `allow_failure: false` option, and this job is not finished,
GitLab can't populate listed pages with the data from security reports.
In this case, [the vulnerability report](vulnerability_report/_index.md) and [the Dependency List](dependency_list/_index.md)
pages are empty.
These security pages can be populated by running the jobs from the manual step of the pipeline.
There is [an issue open to handle this scenario](https://gitlab.com/gitlab-org/gitlab/-/issues/346843).
You can upvote the issue to help with prioritization, and
[contributions are welcomed](https://about.gitlab.com/community/contribute/).
|
https://docs.gitlab.com/user/application_security/on-demand_scan
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/on-demand_scan.md
|
2025-08-13
|
doc/user/application_security/dast
|
[
"doc",
"user",
"application_security",
"dast"
] |
on-demand_scan.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
DAST on-demand scan
| null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
Do not run DAST scans against a production server. Not only can it perform any function that a user can, such
as clicking buttons or submitting forms, but it may also trigger bugs, leading to modification or loss of production data.
Only run DAST scans against a test server.
{{< /alert >}}
## On-demand scans
{{< history >}}
- Runner tags selection [enabled on GitLab.com and GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111499) in GitLab 16.3.
- Browser based on-demand DAST scans available in GitLab 17.0 and later because [proxy-based DAST was removed in the same version](../../../update/deprecations.md#proxy-based-dast-deprecated).
{{< /history >}}
An on-demand DAST scan runs outside the DevOps lifecycle. Changes in your repository don't trigger
the scan. You must either start it manually, or schedule it to run. For on-demand DAST scans,
a [site profile](profiles.md#site-profile) defines **what** is to be scanned, and a
[scanner profile](profiles.md#scanner-profile) defines **how** the application is to be scanned.
An on-demand scan can be run in active or passive mode:
- **Passive mode**: The default mode, which runs a [Passive Browser based scan](browser/_index.md#passive-scans).
- **Active mode**: Runs an [Active Browser based scan](browser/_index.md#active-scans) which is potentially harmful to the site being scanned. To
minimize the risk of accidental damage, running an active scan requires a
[validated site profile](profiles.md#site-profile-validation).
### View on-demand DAST scans
To view on-demand scans:
1. On the left sidebar, select **Search or go to** and find your project or group.
1. Select **Secure > On-demand scans**.
On-demand scans are grouped by their status. The scan library contains all available on-demand
scans.
### Run an on-demand DAST scan
Prerequisites:
- You must have permission to run an on-demand DAST scan against a protected branch. The default
branch is automatically protected. For more information, see
[Pipeline security on protected branches](../../../ci/pipelines/_index.md#pipeline-security-on-protected-branches).
To run an existing on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the scan's row, select **Run scan**.
If the branch saved in the scan no longer exists, you must:
1. [Edit the scan](#edit-an-on-demand-scan).
1. Select a new branch.
1. Save the edited scan.
The on-demand DAST scan runs, and the project's dashboard shows the results.
#### Create an on-demand scan
Create an on-demand scan to:
- Run it immediately.
- Save it to be run in the future.
- Schedule it to be run at a specified schedule.
To create an on-demand DAST scan:
1. On the left sidebar, select **Search or go to** and find your project or group.
1. Select **Secure > On-demand scans**.
1. Select **New scan**.
1. Complete the **Scan name** and **Description** fields.
1. In the **Branch** dropdown list, select the desired branch.
1. Optional. Select the runner tags.
1. Select **Select scanner profile** or **Change scanner profile** to open the drawer, and either:
- Select a scanner profile from the drawer, **or**
- Select **New profile**, create a [scanner profile](profiles.md#scanner-profile), then select **Save profile**.
1. Select **Select site profile** or **Change site profile** to open the drawer, and either:
- Select a site profile from the **Site profile library** drawer, or
- Select **New profile**, create a [site profile](profiles.md#site-profile), then select **Save profile**.
1. To run the on-demand scan:
- Immediately, select **Save and run scan**.
- In the future, select **Save scan**.
- On a schedule:
- Turn on the **Enable scan schedule** toggle.
- Complete the schedule fields.
- Select **Save scan**.
The on-demand DAST scan runs as specified and the project's dashboard shows the results.
### View details of an on-demand scan
Prerequisites:
- You must be able to push to the branch associated with the DAST scan.
To view details of an on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the saved scan's row select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Edit**.
### Edit an on-demand scan
Prerequisites:
- You must be able to push to the branch associated with the DAST scan.
To edit an on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the saved scan's row select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Edit**.
1. Edit the saved scan's details.
1. Select **Save scan**.
### Delete an on-demand scan
Prerequisites:
- You must be able to push to the branch associated with the DAST scan.
To delete an on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the saved scan's row select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Delete**.
1. On the confirmation dialog, select **Delete**.
|
---
stage: Application Security Testing
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
title: DAST on-demand scan
breadcrumbs:
- doc
- user
- application_security
- dast
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
Do not run DAST scans against a production server. Not only can it perform any function that a user can, such
as clicking buttons or submitting forms, but it may also trigger bugs, leading to modification or loss of production data.
Only run DAST scans against a test server.
{{< /alert >}}
## On-demand scans
{{< history >}}
- Runner tags selection [enabled on GitLab.com and GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111499) in GitLab 16.3.
- Browser based on-demand DAST scans available in GitLab 17.0 and later because [proxy-based DAST was removed in the same version](../../../update/deprecations.md#proxy-based-dast-deprecated).
{{< /history >}}
An on-demand DAST scan runs outside the DevOps lifecycle. Changes in your repository don't trigger
the scan. You must either start it manually, or schedule it to run. For on-demand DAST scans,
a [site profile](profiles.md#site-profile) defines **what** is to be scanned, and a
[scanner profile](profiles.md#scanner-profile) defines **how** the application is to be scanned.
An on-demand scan can be run in active or passive mode:
- **Passive mode**: The default mode, which runs a [Passive Browser based scan](browser/_index.md#passive-scans).
- **Active mode**: Runs an [Active Browser based scan](browser/_index.md#active-scans) which is potentially harmful to the site being scanned. To
minimize the risk of accidental damage, running an active scan requires a
[validated site profile](profiles.md#site-profile-validation).
### View on-demand DAST scans
To view on-demand scans:
1. On the left sidebar, select **Search or go to** and find your project or group.
1. Select **Secure > On-demand scans**.
On-demand scans are grouped by their status. The scan library contains all available on-demand
scans.
### Run an on-demand DAST scan
Prerequisites:
- You must have permission to run an on-demand DAST scan against a protected branch. The default
branch is automatically protected. For more information, see
[Pipeline security on protected branches](../../../ci/pipelines/_index.md#pipeline-security-on-protected-branches).
To run an existing on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the scan's row, select **Run scan**.
If the branch saved in the scan no longer exists, you must:
1. [Edit the scan](#edit-an-on-demand-scan).
1. Select a new branch.
1. Save the edited scan.
The on-demand DAST scan runs, and the project's dashboard shows the results.
#### Create an on-demand scan
Create an on-demand scan to:
- Run it immediately.
- Save it to be run in the future.
- Schedule it to be run at a specified schedule.
To create an on-demand DAST scan:
1. On the left sidebar, select **Search or go to** and find your project or group.
1. Select **Secure > On-demand scans**.
1. Select **New scan**.
1. Complete the **Scan name** and **Description** fields.
1. In the **Branch** dropdown list, select the desired branch.
1. Optional. Select the runner tags.
1. Select **Select scanner profile** or **Change scanner profile** to open the drawer, and either:
- Select a scanner profile from the drawer, **or**
- Select **New profile**, create a [scanner profile](profiles.md#scanner-profile), then select **Save profile**.
1. Select **Select site profile** or **Change site profile** to open the drawer, and either:
- Select a site profile from the **Site profile library** drawer, or
- Select **New profile**, create a [site profile](profiles.md#site-profile), then select **Save profile**.
1. To run the on-demand scan:
- Immediately, select **Save and run scan**.
- In the future, select **Save scan**.
- On a schedule:
- Turn on the **Enable scan schedule** toggle.
- Complete the schedule fields.
- Select **Save scan**.
The on-demand DAST scan runs as specified and the project's dashboard shows the results.
### View details of an on-demand scan
Prerequisites:
- You must be able to push to the branch associated with the DAST scan.
To view details of an on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the saved scan's row select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Edit**.
### Edit an on-demand scan
Prerequisites:
- You must be able to push to the branch associated with the DAST scan.
To edit an on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the saved scan's row select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Edit**.
1. Edit the saved scan's details.
1. Select **Save scan**.
### Delete an on-demand scan
Prerequisites:
- You must be able to push to the branch associated with the DAST scan.
To delete an on-demand scan:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > On-demand scans**.
1. Select the **Scan library** tab.
1. In the saved scan's row select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Delete**.
1. On the confirmation dialog, select **Delete**.
|
https://docs.gitlab.com/user/application_security/dast
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md
|
2025-08-13
|
doc/user/application_security/dast
|
[
"doc",
"user",
"application_security",
"dast"
] |
_index.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Dynamic Application Security Testing (DAST)
|
Automated penetration testing, vulnerability detection, web application scanning, security assessment, and CI/CD integration.
|
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
The DAST proxy-based analyzer was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966)
in GitLab 16.9 and [removed](https://gitlab.com/groups/gitlab-org/-/epics/11986) in GitLab 17.3.
This change is a breaking change. For instructions on how to migrate from the DAST proxy-based
analyzer to DAST version 5, see the
[proxy-based migration guide](proxy_based_to_browser_based_migration_guide.md). For instructions on
how to migrate from the DAST version 4 browser-based analyzer to DAST version 5, see the
[browser-based migration guide](browser_based_4_to_5_migration_guide.md).
{{< /alert >}}
Dynamic Application Security Testing (DAST) runs automated penetration tests to find vulnerabilities
in your web applications and APIs as they are running. DAST automates a hacker's approach and
simulates real-world attacks for critical threats such as cross-site scripting (XSS), SQL injection
(SQLi), and cross-site request forgery (CSRF) to uncover vulnerabilities and misconfigurations that
other security tools cannot detect.
DAST is completely language-neutral and examines your application from the outside in. DAST scans
can be run in a CI/CD pipeline, on a schedule, or run manually on demand. Using DAST during the
software development lifecycle enables you to uncover vulnerabilities in your application before
deployment in production. DAST is a foundational component of software security and should be used
together with the other GitLab security tools to provide a comprehensive security assessment of your
applications.
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For an overview, see [Dynamic Application Security Testing (DAST) - Advanced Security Testing](https://www.youtube.com/watch?v=nbeDUoLZJTo).
## GitLab DAST
GitLab DAST and API security analyzers are proprietary runtime tools, which provide broad security
coverage for modern-day web applications and APIs.
Use the DAST analyzers according to your needs:
- To scan web-based applications, including single page web applications, for known vulnerabilities,
use the [DAST](browser/_index.md) analyzer.
- To scan APIs for known vulnerabilities, use the [API security](../api_security_testing/_index.md)
analyzer. Technologies such as GraphQL, REST, and SOAP are supported.
Analyzers follow the architectural patterns described in [Secure your application](../_index.md).
Each analyzer can be configured in the pipeline by using a CI/CD template and runs the scan in a
Docker container. Scans output a
[DAST report artifact](../../../ci/yaml/artifacts_reports.md#artifactsreportsdast) which GitLab uses
to determine discovered vulnerabilities based on differences between scan results on the source and
target branches.
## View scan results
Detected vulnerabilities appear in [merge requests](../detect/security_scanning_results.md), the [pipeline security tab](../detect/security_scanning_results.md),
and the [vulnerability report](../vulnerability_report/_index.md).
{{< alert type="note" >}}
A pipeline may consist of multiple jobs, including SAST and DAST scanning. If any job
fails to finish for any reason, the security dashboard doesn't show DAST scanner output. For
example, if the DAST job finishes but the SAST job fails, the security dashboard doesn't show DAST
results. On failure, the analyzer outputs an
exit code.
{{< /alert >}}
### List URLs scanned
When DAST completes scanning, the merge request page states the number of URLs scanned.
Select **View details** to view the web console output which includes the list of scanned URLs.
|
---
stage: Application Security Testing
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
title: Dynamic Application Security Testing (DAST)
description: Automated penetration testing, vulnerability detection, web application
scanning, security assessment, and CI/CD integration.
breadcrumbs:
- doc
- user
- application_security
- dast
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
The DAST proxy-based analyzer was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966)
in GitLab 16.9 and [removed](https://gitlab.com/groups/gitlab-org/-/epics/11986) in GitLab 17.3.
This change is a breaking change. For instructions on how to migrate from the DAST proxy-based
analyzer to DAST version 5, see the
[proxy-based migration guide](proxy_based_to_browser_based_migration_guide.md). For instructions on
how to migrate from the DAST version 4 browser-based analyzer to DAST version 5, see the
[browser-based migration guide](browser_based_4_to_5_migration_guide.md).
{{< /alert >}}
Dynamic Application Security Testing (DAST) runs automated penetration tests to find vulnerabilities
in your web applications and APIs as they are running. DAST automates a hacker's approach and
simulates real-world attacks for critical threats such as cross-site scripting (XSS), SQL injection
(SQLi), and cross-site request forgery (CSRF) to uncover vulnerabilities and misconfigurations that
other security tools cannot detect.
DAST is completely language-neutral and examines your application from the outside in. DAST scans
can be run in a CI/CD pipeline, on a schedule, or run manually on demand. Using DAST during the
software development lifecycle enables you to uncover vulnerabilities in your application before
deployment in production. DAST is a foundational component of software security and should be used
together with the other GitLab security tools to provide a comprehensive security assessment of your
applications.
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For an overview, see [Dynamic Application Security Testing (DAST) - Advanced Security Testing](https://www.youtube.com/watch?v=nbeDUoLZJTo).
## GitLab DAST
GitLab DAST and API security analyzers are proprietary runtime tools, which provide broad security
coverage for modern-day web applications and APIs.
Use the DAST analyzers according to your needs:
- To scan web-based applications, including single page web applications, for known vulnerabilities,
use the [DAST](browser/_index.md) analyzer.
- To scan APIs for known vulnerabilities, use the [API security](../api_security_testing/_index.md)
analyzer. Technologies such as GraphQL, REST, and SOAP are supported.
Analyzers follow the architectural patterns described in [Secure your application](../_index.md).
Each analyzer can be configured in the pipeline by using a CI/CD template and runs the scan in a
Docker container. Scans output a
[DAST report artifact](../../../ci/yaml/artifacts_reports.md#artifactsreportsdast) which GitLab uses
to determine discovered vulnerabilities based on differences between scan results on the source and
target branches.
## View scan results
Detected vulnerabilities appear in [merge requests](../detect/security_scanning_results.md), the [pipeline security tab](../detect/security_scanning_results.md),
and the [vulnerability report](../vulnerability_report/_index.md).
{{< alert type="note" >}}
A pipeline may consist of multiple jobs, including SAST and DAST scanning. If any job
fails to finish for any reason, the security dashboard doesn't show DAST scanner output. For
example, if the DAST job finishes but the SAST job fails, the security dashboard doesn't show DAST
results. On failure, the analyzer outputs an
exit code.
{{< /alert >}}
### List URLs scanned
When DAST completes scanning, the merge request page states the number of URLs scanned.
Select **View details** to view the web console output which includes the list of scanned URLs.
|
https://docs.gitlab.com/user/application_security/browser_based_4_to_5_migration_guide
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/browser_based_4_to_5_migration_guide.md
|
2025-08-13
|
doc/user/application_security/dast
|
[
"doc",
"user",
"application_security",
"dast"
] |
browser_based_4_to_5_migration_guide.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Migrating from the DAST version 4 browser-based analyzer to DAST version 5
| null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The [DAST proxy-based analyzer](proxy_based_to_browser_based_migration_guide.md) was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966) in GitLab 16.6 and removed in 17.0.
{{< /history >}}
[DAST version 5](browser/_index.md) replaces DAST version 4. This document serves as a guide to
migrate from the DAST version 4 browser-based analyzer to DAST version 5.
Follow this migration guide if all the following conditions apply:
1. You use GitLab DAST to run a DAST scan in a CI/CD pipeline.
1. The DAST CI/CD job is configured by including either of the DAST templates `DAST.gitlab-ci.yml` or `DAST.latest.gitlab-ci.yml`.
1. The CI/CD variable `DAST_VERSION` is not set or is set to `4` or less.
1. The CI/CD variable `DAST_BROWSER_SCAN` is set to `true`.
Migrate to DAST version 5 by reading the following sections and making the recommended changes.
## DAST analyzer versions
DAST comes in two major versions: 4 and 5.
Effective from GitLab 17.0 the DAST templates `DAST.gitlab-ci.yml` and `DAST.latest.gitlab-ci.yml` use DAST version 5 by default.
You can continue using DAST version 4, but you should do so only as an interim measure while migrating to DAST version 5. For details, see [Continuing to use version 4](#continuing-to-use-version-4).
Each DAST major version runs different analyzers:
- DAST version 4 can run either the proxy-based or browser-based analyzer, and uses the proxy-based analyzer by default.
- DAST version 5 runs only the browser-based analyzer.
DAST version 5 uses a set of new CI/CD variables. Aliases have been created for the DAST version 4 variables' names.
Changes to make in GitLab 16.11 and earlier:
- To test DAST version 5, set the CI/CD variable `DAST_VERSION` to 5.
- To avoid job failures, do not remove or rename `DAST_WEBSITE`. The `DAST.gitlab-ci.yml` template versions 16.11 and earlier [still use the `DAST_WEBSITE`](https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.5-ee/lib/gitlab/ci/templates/Security/DAST.gitlab-ci.yml?ref_type=tags#L39) variable.
Changes to make in GitLab 17.0 and later:
- After you upgrade to GitLab 17.0, rename `DAST_WEBSITE` to `DAST_TARGET_URL`.
- When you start using new templates that set `DAST_VERSION` to 5, make sure the CI/CD variable `DAST_VERSION` is not set.
## Continuing to use version 4
You can use the DAST version 4 proxy-based analyzer until GitLab 18.0. Bugs and vulnerabilities in this legacy analyzer will not be fixed.
Changes to make:
- To continue using DAST version 4, set the CI/CD variable `DAST_VERSION` variable to 4.
## Artifacts
GitLab 17.0 automatically publishes artifacts produced by DAST version 5 to the DAST CI job.
Changes to make:
- Remove `artifacts` from the CI job definition if you have overridden it to expose the file log, crawl graph, or authentication report.
- CI/CD variables `DAST_BROWSER_FILE_LOG_PATH` and `DAST_FILE_LOG_PATH` are no longer required.
## Vulnerability check coverage
Browser-based DAST version 4 uses proxy-based analyzer checks for active checks not included in the browser-based analyzer.
Browser-based DAST version 5 does not include the proxy-based analyzer, so there is a gap in check coverage when migrating to version 5.
There is one proxy-based active check that the browser-based analyzer does not cover. Migration of
the remaining active check is proposed in
[epic 13411](https://gitlab.com/groups/gitlab-org/-/epics/13411). If you prefer to remain on DAST
version 4 until the last check is migrated, see
[Continuing to use version 4](#continuing-to-use-version-4).
Remaining check:
- CWE-79: Cross-site Scripting (XSS)
Follow the progress of the remaining check in the epic [Remaining active checks for BBD](https://gitlab.com/groups/gitlab-org/-/epics/13411).
## Changes to CI/CD variables
The following table outlines migration actions required for each browser-based analyzer DAST version 4 CI/CD variable.
See [configuration](browser/configuration/_index.md) for more information on configuring the browser-based analyzer.
| DAST version 4 CI/CD variable | Required action | Notes |
|:--------------------------------------------|:-------------------|:----------------------------------------------|
| `DAST_ADVERTISE_SCAN` | Rename | To `DAST_REQUEST_ADVERTISE_SCAN` |
| `DAST_AFTER_LOGIN_ACTIONS` | Rename | To `DAST_AUTH_AFTER_LOGIN_ACTIONS` |
| `DAST_AUTH_COOKIES` | Rename | To `DAST_AUTH_COOKIE_NAMES` |
| `DAST_AUTH_DISABLE_CLEAR_FIELDS` | Rename | To `DAST_AUTH_CLEAR_INPUT_FIELDS` |
| `DAST_AUTH_REPORT` | No action required | |
| `DAST_AUTH_TYPE` | No action required | |
| `DAST_AUTH_URL` | No action required | |
| `DAST_AUTH_VERIFICATION_LOGIN_FORM` | Rename | To `DAST_AUTH_SUCCESS_IF_NO_LOGIN_FORM` |
| `DAST_AUTH_VERIFICATION_SELECTOR` | Rename | To `DAST_AUTH_SUCCESS_IF_ELEMENT_FOUND` |
| `DAST_AUTH_VERIFICATION_URL` | Rename | To `DAST_AUTH_SUCCESS_IF_AT_URL` |
| `DAST_BROWSER_PATH_TO_LOGIN_FORM` | Rename | To `DAST_AUTH_BEFORE_LOGIN_ACTIONS` |
| `DAST_BROWSER_ACTION_STABILITY_TIMEOUT` | Replace | With `DAST_PAGE_DOM_READY_TIMEOUT` |
| `DAST_BROWSER_ACTION_TIMEOUT` | Remove | Not supported |
| `DAST_BROWSER_ALLOWED_HOSTS` | Rename | To `DAST_SCOPE_ALLOW_HOSTS` |
| `DAST_BROWSER_CACHE` | Rename | To `DAST_USE_CACHE` |
| `DAST_BROWSER_COOKIES` | Rename | To `DAST_REQUEST_COOKIES` |
| `DAST_BROWSER_CRAWL_GRAPH` | Rename | To `DAST_CRAWL_GRAPH` |
| `DAST_BROWSER_CRAWL_TIMEOUT` | Rename | To `DAST_CRAWL_TIMEOUT` |
| `DAST_BROWSER_DEVTOOLS_LOG` | Rename | To `DAST_LOG_DEVTOOLS_CONFIG` |
| `DAST_BROWSER_DOM_READY_AFTER_TIMEOUT` | Rename | To `DAST_PAGE_DOM_STABLE_WAIT` |
| `DAST_BROWSER_ELEMENT_TIMEOUT` | Rename | To `DAST_PAGE_ELEMENT_READY_TIMEOUT` |
| `DAST_BROWSER_EXCLUDED_ELEMENTS` | Rename | To `DAST_SCOPE_EXCLUDE_ELEMENTS` |
| `DAST_BROWSER_EXCLUDED_HOSTS` | Rename | To `DAST_SCOPE_EXCLUDE_HOSTS` |
| `DAST_BROWSER_EXTRACT_ELEMENT_TIMEOUT` | Rename | To `DAST_CRAWL_EXTRACT_ELEMENT_TIMEOUT` |
| `DAST_BROWSER_FILE_LOG` | Rename | To `DAST_LOG_FILE_CONFIG` |
| `DAST_BROWSER_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_BROWSER_IGNORED_HOSTS` | Rename | To `DAST_SCOPE_IGNORE_HOSTS` |
| `DAST_BROWSER_INCLUDE_ONLY_RULES` | Rename | To `DAST_CHECKS_TO_RUN` |
| `DAST_BROWSER_LOG` | Rename | To `DAST_LOG_CONFIG` |
| `DAST_BROWSER_LOG_CHROMIUM_OUTPUT` | Rename | To `DAST_LOG_BROWSER_OUTPUT` |
| `DAST_BROWSER_MAX_ACTIONS` | Rename | To `DAST_CRAWL_MAX_ACTIONS` |
| `DAST_BROWSER_MAX_DEPTH` | Rename | To `DAST_CRAWL_MAX_DEPTH` |
| `DAST_BROWSER_MAX_RESPONSE_SIZE_MB` | Rename | To `DAST_PAGE_MAX_RESPONSE_SIZE_MB` |
| `DAST_BROWSER_NAVIGATION_STABILITY_TIMEOUT` | Rename | To `DAST_PAGE_DOM_READY_TIMEOUT` |
| `DAST_BROWSER_NAVIGATION_TIMEOUT` | Rename | To `DAST_PAGE_READY_AFTER_NAVIGATION_TIMEOUT` |
| `DAST_BROWSER_NUMBER_OF_BROWSERS` | Rename | To `DAST_CRAWL_WORKER_COUNT` |
| `DAST_BROWSER_PAGE_LOADING_SELECTOR` | Rename | To `DAST_PAGE_IS_LOADING_ELEMENT` |
| `DAST_BROWSER_PAGE_READY_SELECTOR` | Rename | To `DAST_PAGE_IS_READY_ELEMENT` |
| `DAST_BROWSER_PASSIVE_CHECK_WORKERS` | Rename | To `DAST_PASSIVE_SCAN_WORKER_COUNT` |
| `DAST_BROWSER_SCAN` | Remove | No longer required |
| `DAST_BROWSER_SEARCH_ELEMENT_TIMEOUT` | Rename | To `DAST_CRAWL_SEARCH_ELEMENT_TIMEOUT` |
| `DAST_BROWSER_STABILITY_TIMEOUT` | Rename | To `DAST_PAGE_READY_AFTER_ACTION_TIMEOUT` |
| `DAST_EXCLUDE_RULES` | Rename | To `DAST_CHECKS_TO_EXCLUDE` |
| `DAST_EXCLUDE_URLS` | Rename | To `DAST_SCOPE_EXCLUDE_URLS` |
| `DAST_FF_ENABLE_BAS` | Remove | Not supported |
| `DAST_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_FIRST_SUBMIT_FIELD` | Rename | To `DAST_AUTH_FIRST_SUBMIT_FIELD` |
| `DAST_FULL_SCAN_ENABLED` | Rename | To `DAST_FULL_SCAN` |
| `DAST_PASSWORD` | Rename | To `DAST_AUTH_PASSWORD` |
| `DAST_PASSWORD_FIELD` | Rename | To `DAST_AUTH_PASSWORD_FIELD` |
| `DAST_PATHS` | Rename | To `DAST_TARGET_PATHS` |
| `DAST_PATHS_FILE` | Rename | To `DAST_TARGET_PATHS_FROM_FILE` |
| `DAST_PKCS12_CERTIFICATE_BASE64` | No action required | |
| `DAST_PKCS12_PASSWORD` | No action required | |
| `DAST_REQUEST_HEADERS` | No action required | |
| `DAST_SKIP_TARGET_CHECK` | Rename | To `DAST_TARGET_CHECK_SKIP` |
| `DAST_SUBMIT_FIELD` | Rename | To `DAST_AUTH_SUBMIT_FIELD` |
| `DAST_TARGET_AVAILABILITY_TIMEOUT` | Rename | To `DAST_TARGET_CHECK_TIMEOUT` |
| `DAST_USERNAME` | Rename | To `DAST_AUTH_USERNAME` |
| `DAST_USERNAME_FIELD` | Rename | To `DAST_AUTH_USERNAME_FIELD` |
| `DAST_WEBSITE` | Rename | To `DAST_TARGET_URL`<br/>GitLab Self-Managed: Upgrade your instance to version 17.0 or later before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
|
---
stage: Application Security Testing
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
title: Migrating from the DAST version 4 browser-based analyzer to DAST version 5
breadcrumbs:
- doc
- user
- application_security
- dast
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The [DAST proxy-based analyzer](proxy_based_to_browser_based_migration_guide.md) was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966) in GitLab 16.6 and removed in 17.0.
{{< /history >}}
[DAST version 5](browser/_index.md) replaces DAST version 4. This document serves as a guide to
migrate from the DAST version 4 browser-based analyzer to DAST version 5.
Follow this migration guide if all the following conditions apply:
1. You use GitLab DAST to run a DAST scan in a CI/CD pipeline.
1. The DAST CI/CD job is configured by including either of the DAST templates `DAST.gitlab-ci.yml` or `DAST.latest.gitlab-ci.yml`.
1. The CI/CD variable `DAST_VERSION` is not set or is set to `4` or less.
1. The CI/CD variable `DAST_BROWSER_SCAN` is set to `true`.
Migrate to DAST version 5 by reading the following sections and making the recommended changes.
## DAST analyzer versions
DAST comes in two major versions: 4 and 5.
Effective from GitLab 17.0 the DAST templates `DAST.gitlab-ci.yml` and `DAST.latest.gitlab-ci.yml` use DAST version 5 by default.
You can continue using DAST version 4, but you should do so only as an interim measure while migrating to DAST version 5. For details, see [Continuing to use version 4](#continuing-to-use-version-4).
Each DAST major version runs different analyzers:
- DAST version 4 can run either the proxy-based or browser-based analyzer, and uses the proxy-based analyzer by default.
- DAST version 5 runs only the browser-based analyzer.
DAST version 5 uses a set of new CI/CD variables. Aliases have been created for the DAST version 4 variables' names.
Changes to make in GitLab 16.11 and earlier:
- To test DAST version 5, set the CI/CD variable `DAST_VERSION` to 5.
- To avoid job failures, do not remove or rename `DAST_WEBSITE`. The `DAST.gitlab-ci.yml` template versions 16.11 and earlier [still use the `DAST_WEBSITE`](https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.5-ee/lib/gitlab/ci/templates/Security/DAST.gitlab-ci.yml?ref_type=tags#L39) variable.
Changes to make in GitLab 17.0 and later:
- After you upgrade to GitLab 17.0, rename `DAST_WEBSITE` to `DAST_TARGET_URL`.
- When you start using new templates that set `DAST_VERSION` to 5, make sure the CI/CD variable `DAST_VERSION` is not set.
## Continuing to use version 4
You can use the DAST version 4 proxy-based analyzer until GitLab 18.0. Bugs and vulnerabilities in this legacy analyzer will not be fixed.
Changes to make:
- To continue using DAST version 4, set the CI/CD variable `DAST_VERSION` variable to 4.
## Artifacts
GitLab 17.0 automatically publishes artifacts produced by DAST version 5 to the DAST CI job.
Changes to make:
- Remove `artifacts` from the CI job definition if you have overridden it to expose the file log, crawl graph, or authentication report.
- CI/CD variables `DAST_BROWSER_FILE_LOG_PATH` and `DAST_FILE_LOG_PATH` are no longer required.
## Vulnerability check coverage
Browser-based DAST version 4 uses proxy-based analyzer checks for active checks not included in the browser-based analyzer.
Browser-based DAST version 5 does not include the proxy-based analyzer, so there is a gap in check coverage when migrating to version 5.
There is one proxy-based active check that the browser-based analyzer does not cover. Migration of
the remaining active check is proposed in
[epic 13411](https://gitlab.com/groups/gitlab-org/-/epics/13411). If you prefer to remain on DAST
version 4 until the last check is migrated, see
[Continuing to use version 4](#continuing-to-use-version-4).
Remaining check:
- CWE-79: Cross-site Scripting (XSS)
Follow the progress of the remaining check in the epic [Remaining active checks for BBD](https://gitlab.com/groups/gitlab-org/-/epics/13411).
## Changes to CI/CD variables
The following table outlines migration actions required for each browser-based analyzer DAST version 4 CI/CD variable.
See [configuration](browser/configuration/_index.md) for more information on configuring the browser-based analyzer.
| DAST version 4 CI/CD variable | Required action | Notes |
|:--------------------------------------------|:-------------------|:----------------------------------------------|
| `DAST_ADVERTISE_SCAN` | Rename | To `DAST_REQUEST_ADVERTISE_SCAN` |
| `DAST_AFTER_LOGIN_ACTIONS` | Rename | To `DAST_AUTH_AFTER_LOGIN_ACTIONS` |
| `DAST_AUTH_COOKIES` | Rename | To `DAST_AUTH_COOKIE_NAMES` |
| `DAST_AUTH_DISABLE_CLEAR_FIELDS` | Rename | To `DAST_AUTH_CLEAR_INPUT_FIELDS` |
| `DAST_AUTH_REPORT` | No action required | |
| `DAST_AUTH_TYPE` | No action required | |
| `DAST_AUTH_URL` | No action required | |
| `DAST_AUTH_VERIFICATION_LOGIN_FORM` | Rename | To `DAST_AUTH_SUCCESS_IF_NO_LOGIN_FORM` |
| `DAST_AUTH_VERIFICATION_SELECTOR` | Rename | To `DAST_AUTH_SUCCESS_IF_ELEMENT_FOUND` |
| `DAST_AUTH_VERIFICATION_URL` | Rename | To `DAST_AUTH_SUCCESS_IF_AT_URL` |
| `DAST_BROWSER_PATH_TO_LOGIN_FORM` | Rename | To `DAST_AUTH_BEFORE_LOGIN_ACTIONS` |
| `DAST_BROWSER_ACTION_STABILITY_TIMEOUT` | Replace | With `DAST_PAGE_DOM_READY_TIMEOUT` |
| `DAST_BROWSER_ACTION_TIMEOUT` | Remove | Not supported |
| `DAST_BROWSER_ALLOWED_HOSTS` | Rename | To `DAST_SCOPE_ALLOW_HOSTS` |
| `DAST_BROWSER_CACHE` | Rename | To `DAST_USE_CACHE` |
| `DAST_BROWSER_COOKIES` | Rename | To `DAST_REQUEST_COOKIES` |
| `DAST_BROWSER_CRAWL_GRAPH` | Rename | To `DAST_CRAWL_GRAPH` |
| `DAST_BROWSER_CRAWL_TIMEOUT` | Rename | To `DAST_CRAWL_TIMEOUT` |
| `DAST_BROWSER_DEVTOOLS_LOG` | Rename | To `DAST_LOG_DEVTOOLS_CONFIG` |
| `DAST_BROWSER_DOM_READY_AFTER_TIMEOUT` | Rename | To `DAST_PAGE_DOM_STABLE_WAIT` |
| `DAST_BROWSER_ELEMENT_TIMEOUT` | Rename | To `DAST_PAGE_ELEMENT_READY_TIMEOUT` |
| `DAST_BROWSER_EXCLUDED_ELEMENTS` | Rename | To `DAST_SCOPE_EXCLUDE_ELEMENTS` |
| `DAST_BROWSER_EXCLUDED_HOSTS` | Rename | To `DAST_SCOPE_EXCLUDE_HOSTS` |
| `DAST_BROWSER_EXTRACT_ELEMENT_TIMEOUT` | Rename | To `DAST_CRAWL_EXTRACT_ELEMENT_TIMEOUT` |
| `DAST_BROWSER_FILE_LOG` | Rename | To `DAST_LOG_FILE_CONFIG` |
| `DAST_BROWSER_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_BROWSER_IGNORED_HOSTS` | Rename | To `DAST_SCOPE_IGNORE_HOSTS` |
| `DAST_BROWSER_INCLUDE_ONLY_RULES` | Rename | To `DAST_CHECKS_TO_RUN` |
| `DAST_BROWSER_LOG` | Rename | To `DAST_LOG_CONFIG` |
| `DAST_BROWSER_LOG_CHROMIUM_OUTPUT` | Rename | To `DAST_LOG_BROWSER_OUTPUT` |
| `DAST_BROWSER_MAX_ACTIONS` | Rename | To `DAST_CRAWL_MAX_ACTIONS` |
| `DAST_BROWSER_MAX_DEPTH` | Rename | To `DAST_CRAWL_MAX_DEPTH` |
| `DAST_BROWSER_MAX_RESPONSE_SIZE_MB` | Rename | To `DAST_PAGE_MAX_RESPONSE_SIZE_MB` |
| `DAST_BROWSER_NAVIGATION_STABILITY_TIMEOUT` | Rename | To `DAST_PAGE_DOM_READY_TIMEOUT` |
| `DAST_BROWSER_NAVIGATION_TIMEOUT` | Rename | To `DAST_PAGE_READY_AFTER_NAVIGATION_TIMEOUT` |
| `DAST_BROWSER_NUMBER_OF_BROWSERS` | Rename | To `DAST_CRAWL_WORKER_COUNT` |
| `DAST_BROWSER_PAGE_LOADING_SELECTOR` | Rename | To `DAST_PAGE_IS_LOADING_ELEMENT` |
| `DAST_BROWSER_PAGE_READY_SELECTOR` | Rename | To `DAST_PAGE_IS_READY_ELEMENT` |
| `DAST_BROWSER_PASSIVE_CHECK_WORKERS` | Rename | To `DAST_PASSIVE_SCAN_WORKER_COUNT` |
| `DAST_BROWSER_SCAN` | Remove | No longer required |
| `DAST_BROWSER_SEARCH_ELEMENT_TIMEOUT` | Rename | To `DAST_CRAWL_SEARCH_ELEMENT_TIMEOUT` |
| `DAST_BROWSER_STABILITY_TIMEOUT` | Rename | To `DAST_PAGE_READY_AFTER_ACTION_TIMEOUT` |
| `DAST_EXCLUDE_RULES` | Rename | To `DAST_CHECKS_TO_EXCLUDE` |
| `DAST_EXCLUDE_URLS` | Rename | To `DAST_SCOPE_EXCLUDE_URLS` |
| `DAST_FF_ENABLE_BAS` | Remove | Not supported |
| `DAST_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_FIRST_SUBMIT_FIELD` | Rename | To `DAST_AUTH_FIRST_SUBMIT_FIELD` |
| `DAST_FULL_SCAN_ENABLED` | Rename | To `DAST_FULL_SCAN` |
| `DAST_PASSWORD` | Rename | To `DAST_AUTH_PASSWORD` |
| `DAST_PASSWORD_FIELD` | Rename | To `DAST_AUTH_PASSWORD_FIELD` |
| `DAST_PATHS` | Rename | To `DAST_TARGET_PATHS` |
| `DAST_PATHS_FILE` | Rename | To `DAST_TARGET_PATHS_FROM_FILE` |
| `DAST_PKCS12_CERTIFICATE_BASE64` | No action required | |
| `DAST_PKCS12_PASSWORD` | No action required | |
| `DAST_REQUEST_HEADERS` | No action required | |
| `DAST_SKIP_TARGET_CHECK` | Rename | To `DAST_TARGET_CHECK_SKIP` |
| `DAST_SUBMIT_FIELD` | Rename | To `DAST_AUTH_SUBMIT_FIELD` |
| `DAST_TARGET_AVAILABILITY_TIMEOUT` | Rename | To `DAST_TARGET_CHECK_TIMEOUT` |
| `DAST_USERNAME` | Rename | To `DAST_AUTH_USERNAME` |
| `DAST_USERNAME_FIELD` | Rename | To `DAST_AUTH_USERNAME_FIELD` |
| `DAST_WEBSITE` | Rename | To `DAST_TARGET_URL`<br/>GitLab Self-Managed: Upgrade your instance to version 17.0 or later before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
|
https://docs.gitlab.com/user/application_security/profiles
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/profiles.md
|
2025-08-13
|
doc/user/application_security/dast
|
[
"doc",
"user",
"application_security",
"dast"
] |
profiles.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
DAST profiles
| null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
DAST site and scanner profiles save information related to your applications and the scanners you use to evaluate them.
Once you define a profile, you can use it for pipeline and on-demand DAST jobs.
The creation, updating, and deletion of DAST profiles, DAST scanner profiles,
and DAST site profiles are included in the [audit log](../../../administration/compliance/audit_event_reports.md).
## Site profile
{{< history >}}
- Site profile features, scan method and file URL, were [enabled on GitLab.com and GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/345837) in GitLab 15.6.
- GraphQL endpoint path feature was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/378692) in GitLab 15.7.
- Additional variables [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/177703) in GitLab 17.9.
{{< /history >}}
A site profile defines the attributes and configuration details of the deployed application,
website, or API to be scanned by DAST.
A site profile contains:
- **Profile name**: A name you assign to the site to be scanned. While a site profile is referenced
in either `.gitlab-ci.yml` or an on-demand scan, it **cannot** be renamed.
- **Site type**: The type of target to be scanned, either website or API scan.
- **Target URL**: The URL that DAST runs against.
- **Excluded URLs**: A comma-separated list of URLs to exclude from the scan.
You can use [RE2-style regex](https://github.com/google/re2/wiki/Syntax). The regex can't include the question mark (`?`) character, because it is a valid URL character.
- **Request headers**: A comma-separated list of HTTP request headers, including names and values. These headers are added to every request made by DAST.
- **Authentication**:
- **Authenticated URL**: The URL of the page containing the sign-in HTML form on the target website. The username and password are submitted with the login form to create an authenticated scan.
- **Username**: The username used to authenticate to the website.
- **Password**: The password used to authenticate to the website.
- **Username form field**: The name of username field at the sign-in HTML form.
- **Password form field**: The name of password field at the sign-in HTML form.
- **Submit form field**: The `id` or `name` of the element that when selected submits the sign-in HTML form.
- **Scan method**: A type of method to perform API testing. The supported methods are OpenAPI, Postman Collections, HTTP Archive (HAR), or GraphQL.
- **GraphQL endpoint path**: The path to the GraphQL endpoint. This path is concatenated with the target URL to provide the URI for the scan to test. The GraphQL endpoint must support introspection queries.
- **File URL**: The URL of the OpenAPI, Postman Collection, or HTTP Archive file.
- **Additional variables**: A list of environment variables to configure specific scan behaviors. These variables provide the same configuration options as pipeline-based DAST scans, such as setting timeouts, adding an authentication success URL, or enabling advanced scan features.
When an API site type is selected, a host override is used to ensure the API being scanned is on the same host as the target. This is done to reduce the risk of running an active scan against the wrong API.
When configured, request headers and password fields are encrypted using [`aes-256-gcm`](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) before being stored in the database.
This data can only be read and decrypted with a valid secrets file.
You can reference a site profile in `.gitlab-ci.yml` and
on-demand scans.
```yaml
stages:
- dast
include:
- template: DAST.gitlab-ci.yml
dast:
stage: dast
dast_configuration:
site_profile: "<profile name>"
```
### Site profile validation
Site profile validation reduces the risk of running an active scan against the wrong website. A site
must be validated before an active scan can run against it. Site profile validation is not a security feature.
If necessary, you can run an active DAST scan without validation by using a
[pipeline scan](browser/configuration/enabling_the_analyzer.md).
Each of the site validation methods are equivalent in functionality, so use whichever is most suitable:
- **Text file validation**: Requires a text file be uploaded to the target site. The text file is
allocated a name and content that is unique to the project. The validation process checks the
file's content.
- **Header validation**: Requires the header `Gitlab-On-Demand-DAST` be added to the target site,
with a value unique to the project. The validation process checks that the header is present, and
checks its value.
- **Meta tag validation**: Requires the meta tag named `gitlab-dast-validation` be added to the
target site, with a value unique to the project. Make sure it's added to the `<head>` section of
the page. The validation process checks that the meta tag is present, and checks its value.
### Create a site profile
To create a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select **New > Site profile**.
1. Complete the fields then select **Save profile**.
The site profile is saved, for use in an on-demand scan.
### Edit a site profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a site profile is linked to a security policy, you cannot edit the profile from this page. See
[Scan execution policies](../policies/scan_execution_policies.md) for more information.
{{< /alert >}}
{{< alert type="note" >}}
If a site profile's Target URL or Authenticated URL is updated, the request headers and password fields associated with that profile are cleared.
{{< /alert >}}
When a validated site profile's file, header, or meta tag is edited, the site's
[validation status](#site-profile-validation) is revoked.
To edit a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Edit**.
1. Edit the fields then select **Save profile**.
### Delete a site profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a site profile is linked to a security policy, a user cannot delete the profile from this page.
See [Scan execution policies](../policies/scan_execution_policies.md) for more information.
{{< /alert >}}
To delete a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Delete**.
1. Select **Delete** to confirm the deletion.
### Validate a site profile
Validating a site is required to run an active scan.
Prerequisites:
- A runner must be available in the project to run a validation job.
To validate a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row, select **Validate**.
1. Select the validation method.
1. For **Text file validation**:
1. Download the validation file listed in **Step 2**.
1. Upload the validation file to the host, to the location in **Step 3** or any location you
prefer.
1. If required, edit the file location in **Step 3**.
1. Select **Validate**.
1. For **Header validation**:
1. Select the clipboard icon in **Step 2**.
1. Edit the header of the site to validate, and paste the clipboard content.
1. Select the input field in **Step 3** and enter the location of the header.
1. Select **Validate**.
1. For **Meta tag validation**:
1. Select the clipboard icon in **Step 2**.
1. Edit the content of the site to validate, and paste the clipboard content.
1. Select the input field in **Step 3** and enter the location of the meta tag.
1. Select **Validate**.
The site is validated and an active scan can run against it. A site profile's validation status is
revoked only when it's revoked manually, or its file, header, or meta tag is edited.
### Retry a failed validation
Failed site validation attempts are listed on the **Site profiles** tab of the **Manage profiles**
page.
To retry a site profile's failed validation:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row, select **Retry validation**.
### Revoke a site profile's validation status
{{< alert type="warning" >}}
When a site profile's validation status is revoked, all site profiles that share the same URL also
have their validation status revoked.
{{< /alert >}}
To revoke a site profile's validation status:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Beside the validated profile, select **Revoke validation**.
The site profile's validation status is revoked.
### Validated site profile headers
The following are code samples of how you can provide the required site profile header in your
application.
#### Ruby on Rails example for on-demand scan
Here's how you can add a custom header in a Ruby on Rails application:
```ruby
class DastWebsiteTargetController < ActionController::Base
def dast_website_target
response.headers['Gitlab-On-Demand-DAST'] = '0dd79c9a-7b29-4e26-a815-eaaf53fcab1c'
head :ok
end
end
```
#### Django example for on-demand scan
Here's how you can add a
[custom header in Django](https://docs.djangoproject.com/en/2.2/ref/request-response/#setting-header-fields):
```python
class DastWebsiteTargetView(View):
def head(self, *args, **kwargs):
response = HttpResponse()
response['Gitlab-On-Demand-DAST'] = '0dd79c9a-7b29-4e26-a815-eaaf53fcab1c'
return response
```
#### Node (with Express) example for on-demand scan
Here's how you can add a
[custom header in Node (with Express)](https://expressjs.com/en/5x/api.html#res.append):
```javascript
app.get('/dast-website-target', function(req, res) {
res.append('Gitlab-On-Demand-DAST', '0dd79c9a-7b29-4e26-a815-eaaf53fcab1c')
res.send('Respond to DAST ping')
})
```
## Scanner profile
{{< history >}}
- Deprecated AJAX Spider option with the introduction of Browser based on-demand DAST scans in GitLab 17.0.
- Renamed spider timeout to crawl timeout with the introduction of Browser based on-demand DAST scans in GitLab 17.0.
{{< /history >}}
A scanner profile defines the configuration details of a security scanner.
A scanner profile contains:
- **Profile name**: A name you give the scanner profile. For example, "Spider_15". While a scanner
profile is referenced in either `.gitlab-ci.yml` or an on-demand scan, it **cannot** be renamed.
- **Scan mode**: A passive scan monitors all HTTP messages (requests and responses) sent to the target. An active scan attacks the target to find potential vulnerabilities.
- **Crawl timeout**: The maximum number of minutes allowed for the crawler to traverse the site.
- **Target timeout**: The maximum number of seconds DAST waits for the site to be available before
starting the scan.
- **Debug messages**: Include debug messages in the DAST console output.
You can reference a scanner profile in `.gitlab-ci.yml` and
on-demand scans.
```yaml
stages:
- dast
include:
- template: DAST.gitlab-ci.yml
dast:
stage: dast
dast_configuration:
scanner_profile: "<profile name>"
```
### Create a scanner profile
To create a scanner profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select **New > Scanner profile**.
1. Complete the form. For details of each field, see [Scanner profile](#scanner-profile).
1. Select **Save profile**.
### Edit a scanner profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a scanner profile is linked to a security policy, you cannot edit the profile from this page.
For more information, see [Scan execution policies](../policies/scan_execution_policies.md).
{{< /alert >}}
To edit a scanner profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Scanner profiles** tab.
1. In the scanner's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Edit**.
1. Edit the form.
1. Select **Save profile**.
### Delete a scanner profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a scanner profile is linked to a security policy, a user cannot delete the profile from this
page. For more information, see [Scan execution policies](../policies/scan_execution_policies.md).
{{< /alert >}}
To delete a scanner profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Scanner profiles** tab.
1. In the scanner's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Delete**.
1. Select **Delete**.
|
---
stage: Application Security Testing
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
title: DAST profiles
breadcrumbs:
- doc
- user
- application_security
- dast
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
DAST site and scanner profiles save information related to your applications and the scanners you use to evaluate them.
Once you define a profile, you can use it for pipeline and on-demand DAST jobs.
The creation, updating, and deletion of DAST profiles, DAST scanner profiles,
and DAST site profiles are included in the [audit log](../../../administration/compliance/audit_event_reports.md).
## Site profile
{{< history >}}
- Site profile features, scan method and file URL, were [enabled on GitLab.com and GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/345837) in GitLab 15.6.
- GraphQL endpoint path feature was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/378692) in GitLab 15.7.
- Additional variables [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/177703) in GitLab 17.9.
{{< /history >}}
A site profile defines the attributes and configuration details of the deployed application,
website, or API to be scanned by DAST.
A site profile contains:
- **Profile name**: A name you assign to the site to be scanned. While a site profile is referenced
in either `.gitlab-ci.yml` or an on-demand scan, it **cannot** be renamed.
- **Site type**: The type of target to be scanned, either website or API scan.
- **Target URL**: The URL that DAST runs against.
- **Excluded URLs**: A comma-separated list of URLs to exclude from the scan.
You can use [RE2-style regex](https://github.com/google/re2/wiki/Syntax). The regex can't include the question mark (`?`) character, because it is a valid URL character.
- **Request headers**: A comma-separated list of HTTP request headers, including names and values. These headers are added to every request made by DAST.
- **Authentication**:
- **Authenticated URL**: The URL of the page containing the sign-in HTML form on the target website. The username and password are submitted with the login form to create an authenticated scan.
- **Username**: The username used to authenticate to the website.
- **Password**: The password used to authenticate to the website.
- **Username form field**: The name of username field at the sign-in HTML form.
- **Password form field**: The name of password field at the sign-in HTML form.
- **Submit form field**: The `id` or `name` of the element that when selected submits the sign-in HTML form.
- **Scan method**: A type of method to perform API testing. The supported methods are OpenAPI, Postman Collections, HTTP Archive (HAR), or GraphQL.
- **GraphQL endpoint path**: The path to the GraphQL endpoint. This path is concatenated with the target URL to provide the URI for the scan to test. The GraphQL endpoint must support introspection queries.
- **File URL**: The URL of the OpenAPI, Postman Collection, or HTTP Archive file.
- **Additional variables**: A list of environment variables to configure specific scan behaviors. These variables provide the same configuration options as pipeline-based DAST scans, such as setting timeouts, adding an authentication success URL, or enabling advanced scan features.
When an API site type is selected, a host override is used to ensure the API being scanned is on the same host as the target. This is done to reduce the risk of running an active scan against the wrong API.
When configured, request headers and password fields are encrypted using [`aes-256-gcm`](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) before being stored in the database.
This data can only be read and decrypted with a valid secrets file.
You can reference a site profile in `.gitlab-ci.yml` and
on-demand scans.
```yaml
stages:
- dast
include:
- template: DAST.gitlab-ci.yml
dast:
stage: dast
dast_configuration:
site_profile: "<profile name>"
```
### Site profile validation
Site profile validation reduces the risk of running an active scan against the wrong website. A site
must be validated before an active scan can run against it. Site profile validation is not a security feature.
If necessary, you can run an active DAST scan without validation by using a
[pipeline scan](browser/configuration/enabling_the_analyzer.md).
Each of the site validation methods are equivalent in functionality, so use whichever is most suitable:
- **Text file validation**: Requires a text file be uploaded to the target site. The text file is
allocated a name and content that is unique to the project. The validation process checks the
file's content.
- **Header validation**: Requires the header `Gitlab-On-Demand-DAST` be added to the target site,
with a value unique to the project. The validation process checks that the header is present, and
checks its value.
- **Meta tag validation**: Requires the meta tag named `gitlab-dast-validation` be added to the
target site, with a value unique to the project. Make sure it's added to the `<head>` section of
the page. The validation process checks that the meta tag is present, and checks its value.
### Create a site profile
To create a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select **New > Site profile**.
1. Complete the fields then select **Save profile**.
The site profile is saved, for use in an on-demand scan.
### Edit a site profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a site profile is linked to a security policy, you cannot edit the profile from this page. See
[Scan execution policies](../policies/scan_execution_policies.md) for more information.
{{< /alert >}}
{{< alert type="note" >}}
If a site profile's Target URL or Authenticated URL is updated, the request headers and password fields associated with that profile are cleared.
{{< /alert >}}
When a validated site profile's file, header, or meta tag is edited, the site's
[validation status](#site-profile-validation) is revoked.
To edit a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Edit**.
1. Edit the fields then select **Save profile**.
### Delete a site profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a site profile is linked to a security policy, a user cannot delete the profile from this page.
See [Scan execution policies](../policies/scan_execution_policies.md) for more information.
{{< /alert >}}
To delete a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Delete**.
1. Select **Delete** to confirm the deletion.
### Validate a site profile
Validating a site is required to run an active scan.
Prerequisites:
- A runner must be available in the project to run a validation job.
To validate a site profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row, select **Validate**.
1. Select the validation method.
1. For **Text file validation**:
1. Download the validation file listed in **Step 2**.
1. Upload the validation file to the host, to the location in **Step 3** or any location you
prefer.
1. If required, edit the file location in **Step 3**.
1. Select **Validate**.
1. For **Header validation**:
1. Select the clipboard icon in **Step 2**.
1. Edit the header of the site to validate, and paste the clipboard content.
1. Select the input field in **Step 3** and enter the location of the header.
1. Select **Validate**.
1. For **Meta tag validation**:
1. Select the clipboard icon in **Step 2**.
1. Edit the content of the site to validate, and paste the clipboard content.
1. Select the input field in **Step 3** and enter the location of the meta tag.
1. Select **Validate**.
The site is validated and an active scan can run against it. A site profile's validation status is
revoked only when it's revoked manually, or its file, header, or meta tag is edited.
### Retry a failed validation
Failed site validation attempts are listed on the **Site profiles** tab of the **Manage profiles**
page.
To retry a site profile's failed validation:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Site Profiles** tab.
1. In the profile's row, select **Retry validation**.
### Revoke a site profile's validation status
{{< alert type="warning" >}}
When a site profile's validation status is revoked, all site profiles that share the same URL also
have their validation status revoked.
{{< /alert >}}
To revoke a site profile's validation status:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Beside the validated profile, select **Revoke validation**.
The site profile's validation status is revoked.
### Validated site profile headers
The following are code samples of how you can provide the required site profile header in your
application.
#### Ruby on Rails example for on-demand scan
Here's how you can add a custom header in a Ruby on Rails application:
```ruby
class DastWebsiteTargetController < ActionController::Base
def dast_website_target
response.headers['Gitlab-On-Demand-DAST'] = '0dd79c9a-7b29-4e26-a815-eaaf53fcab1c'
head :ok
end
end
```
#### Django example for on-demand scan
Here's how you can add a
[custom header in Django](https://docs.djangoproject.com/en/2.2/ref/request-response/#setting-header-fields):
```python
class DastWebsiteTargetView(View):
def head(self, *args, **kwargs):
response = HttpResponse()
response['Gitlab-On-Demand-DAST'] = '0dd79c9a-7b29-4e26-a815-eaaf53fcab1c'
return response
```
#### Node (with Express) example for on-demand scan
Here's how you can add a
[custom header in Node (with Express)](https://expressjs.com/en/5x/api.html#res.append):
```javascript
app.get('/dast-website-target', function(req, res) {
res.append('Gitlab-On-Demand-DAST', '0dd79c9a-7b29-4e26-a815-eaaf53fcab1c')
res.send('Respond to DAST ping')
})
```
## Scanner profile
{{< history >}}
- Deprecated AJAX Spider option with the introduction of Browser based on-demand DAST scans in GitLab 17.0.
- Renamed spider timeout to crawl timeout with the introduction of Browser based on-demand DAST scans in GitLab 17.0.
{{< /history >}}
A scanner profile defines the configuration details of a security scanner.
A scanner profile contains:
- **Profile name**: A name you give the scanner profile. For example, "Spider_15". While a scanner
profile is referenced in either `.gitlab-ci.yml` or an on-demand scan, it **cannot** be renamed.
- **Scan mode**: A passive scan monitors all HTTP messages (requests and responses) sent to the target. An active scan attacks the target to find potential vulnerabilities.
- **Crawl timeout**: The maximum number of minutes allowed for the crawler to traverse the site.
- **Target timeout**: The maximum number of seconds DAST waits for the site to be available before
starting the scan.
- **Debug messages**: Include debug messages in the DAST console output.
You can reference a scanner profile in `.gitlab-ci.yml` and
on-demand scans.
```yaml
stages:
- dast
include:
- template: DAST.gitlab-ci.yml
dast:
stage: dast
dast_configuration:
scanner_profile: "<profile name>"
```
### Create a scanner profile
To create a scanner profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select **New > Scanner profile**.
1. Complete the form. For details of each field, see [Scanner profile](#scanner-profile).
1. Select **Save profile**.
### Edit a scanner profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a scanner profile is linked to a security policy, you cannot edit the profile from this page.
For more information, see [Scan execution policies](../policies/scan_execution_policies.md).
{{< /alert >}}
To edit a scanner profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Scanner profiles** tab.
1. In the scanner's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Edit**.
1. Edit the form.
1. Select **Save profile**.
### Delete a scanner profile
Prerequisites:
- If a DAST scan uses the profile, you must be able to push to the branch associated with the scan.
{{< alert type="note" >}}
If a scanner profile is linked to a security policy, a user cannot delete the profile from this
page. For more information, see [Scan execution policies](../policies/scan_execution_policies.md).
{{< /alert >}}
To delete a scanner profile:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Secure > Security configuration**.
1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**.
1. Select the **Scanner profiles** tab.
1. In the scanner's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Delete**.
1. Select **Delete**.
|
https://docs.gitlab.com/user/application_security/proxy_based_to_browser_based_migration_guide
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/proxy_based_to_browser_based_migration_guide.md
|
2025-08-13
|
doc/user/application_security/dast
|
[
"doc",
"user",
"application_security",
"dast"
] |
proxy_based_to_browser_based_migration_guide.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Migrating from the DAST proxy-based analyzer to DAST version 5
| null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The [DAST proxy-based analyzer](proxy_based_to_browser_based_migration_guide.md) was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966) in GitLab 16.6 and removed in 17.0.
{{< /history >}}
[DAST version 5](browser/_index.md) replaces the proxy-based analyzer with a browser-based analyzer. This document serves as a guide to
migrate from the proxy-based analyzer to DAST version 5.
Follow this migration guide if all the following conditions apply:
1. You use GitLab DAST to run a DAST scan in a CI/CD pipeline.
1. The DAST CI/CD job is configured by including either of the DAST templates `DAST.gitlab-ci.yml` or `DAST.latest.gitlab-ci.yml`.
1. The CI/CD variable `DAST_VERSION` is not set or is set to `4` or less.
1. The CI/CD variable `DAST_BROWSER_SCAN` is not set or is set to `false`.
Migrate to DAST version 5 by reading the following sections and making the recommended changes.
## DAST analyzer versions
DAST comes in two major versions: 4 and 5.
Effective from GitLab 17.0 the DAST templates `DAST.gitlab-ci.yml` and `DAST.latest.gitlab-ci.yml` use DAST version 5 by default.
You can continue using DAST version 4, but you should do so only as an interim measure while migrating to DAST version 5. For details, see [Continuing to use the proxy-based analyzer](#continuing-to-use-the-proxy-based-analyzer).
Each DAST major version uses different analyzers by default:
- DAST version 4 uses the proxy-based analyzer.
- DAST version 5 uses the browser-based analyzer.
DAST version 5 uses a set of new CI/CD variables. Aliases have been created for the DAST version 4 variables' names.
Changes to make:
- To test your DAST scan using DAST version 5 in GitLab 16.11 and earlier, set the CI/CD variable `DAST_VERSION` to `5`.
## Continuing to use the proxy-based analyzer
You can use the proxy-based DAST analyzer until GitLab 18.0. Bugs and vulnerabilities in this legacy analyzer will not be fixed.
Changes to make:
- To continue using the proxy-based analyzer, set the CI/CD variable `DAST_VERSION` variable to `4`.
## Artifacts
GitLab 17.0 automatically publishes artifacts produced by DAST version 5 to the DAST CI job.
Changes to make:
- Remove `artifacts` from the CI job definition if you have overridden it to expose the file log, crawl graph, or authentication report.
- CI/CD variables `DAST_BROWSER_FILE_LOG_PATH` and `DAST_FILE_LOG_PATH` are no longer required.
## Authentication
The proxy-based analyzer and DAST version 5 both use the browser-based analyzer to authenticate. Upgrading
to DAST version 5 does not change how authentication works.
Changes to make:
- Rename authentication CI/CD variables, see variables with the `DAST_AUTH` prefix.
- If not already done, exclude the logout URL from the scan using `DAST_SCOPE_EXCLUDE_URLS`.
## Crawling
DAST version 5 crawls the target application in a browser to provide better crawl coverage. This may require
more resources to run than an equivalent proxy-based analyzer crawl.
Changes to make:
- Use `DAST_TARGET_URL` instead of `DAST_WEBSITE`.
- Use `DAST_CRAWL_TIMEOUT` instead of `DAST_SPIDER_MINS`.
- CI/CD variables `DAST_USE_AJAX_SPIDER`, `DAST_SPIDER_START_AT_HOST`, `DAST_ZAP_CLI_OPTIONS`
and `DAST_ZAP_LOG_CONFIGURATION` are no longer supported.
- Configure `DAST_PAGE_MAX_RESPONSE_SIZE_MB` if DAST should process response bodies larger than 10 MB.
- Consider providing more CPU resources to the GitLab Runner executing the DAST job.
## Scope
DAST version 5 provides more control over scope compared to the proxy-based analyzer.
Changes to make:
- Use `DAST_SCOPE_ALLOW_HOSTS` instead of `DAST_ALLOWED_HOSTS`.
- The domain of `DAST_TARGET_URL` is automatically added to `DAST_SCOPE_ALLOW_HOSTS`, consider adding domains for the
target application API and asset endpoints.
- Remove domains from the scan by adding them to `DAST_SCOPE_EXCLUDE_HOSTS` (except during authentication).
## Vulnerability checks
### Changes required
DAST version 5 uses vulnerability definitions built by GitLab, these do not map directly to proxy-based
analyzer definitions.
Changes to make:
- Use `DAST_CHECKS_TO_RUN` instead of `DAST_ONLY_INCLUDE_RULES`. Change the IDs used to GitLab DAST vulnerability check IDs.
- Use `DAST_CHECKS_TO_EXCLUDE` instead of `DAST_EXCLUDE_RULES`. Change the IDs used to GitLab DAST vulnerability check IDs.
- See [vulnerability check](browser/checks/_index.md) documentation for descriptions and IDs of GitLab DAST vulnerability checks.
- CI/CD variables `DAST_AGGREGATE_VULNERABILITIES` and `DAST_MAX_URLS_PER_VULNERABILITY` are no longer supported.
### Why migrating produces different vulnerabilities
Proxy-based scans and browser-based DAST version 5 scans do not produce the same results because they use a different set of vulnerability checks.
DAST version 5 does not have an equivalent for proxy-based checks that create too many false positives,
are not worth running because modern browsers don't allow the vulnerability to be exploited, or are no longer considered relevant.
DAST version 5 includes checks that proxy-based analyzer does not.
DAST version 5 scans provide better coverage of your application, so they may identify more vulnerabilities because more of your site is scanned.
### Coverage
One proxy-based active check is yet to be implemented in the browser-based DAST analyzer.
Migration of the remaining active check is proposed in
[epic 13411](https://gitlab.com/groups/gitlab-org/-/epics/13411). If you prefer to remain on DAST
version 4 until the last check is migrated, see [Continuing to use the proxy-based analyzer](#continuing-to-use-the-proxy-based-analyzer).
Remaining check:
- CWE-79: Cross-site Scripting (XSS)
## On-demand scans
On-demand scans runs a browser-based scan using [DAST version 5](https://gitlab.com/groups/gitlab-org/-/epics/11429) from GitLab 17.0.
## Troubleshooting
See the DAST version 5 [troubleshooting](browser/troubleshooting.md) documentation.
## Changes to CI/CD variables
The following table outlines migration actions required for each proxy-based analyzer CI/CD variable.
See [configuration](browser/configuration/_index.md) for more information on configuring DAST version 5.
| Proxy-based analyzer CI/CD variable | Required action | Notes |
|:-------------------------------------|:-------------------------|:-----------------------------------------------------------------------------------------|
| `DAST_ADVERTISE_SCAN` | Rename | To `DAST_REQUEST_ADVERTISE_SCAN` |
| `DAST_ALLOWED_HOSTS` | Rename | To `DAST_SCOPE_ALLOW_HOSTS` |
| `DAST_API_HOST_OVERRIDE` | Remove | Not supported |
| `DAST_API_SPECIFICATION` | Remove | Not supported |
| `DAST_AUTH_EXCLUDE_URLS` | Rename | To `DAST_SCOPE_EXCLUDE_URLS` |
| `DAST_AUTO_UPDATE_ADDONS` | Remove | Not supported |
| `DAST_BROWSER_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_DEBUG` | Remove | Not supported |
| `DAST_EXCLUDE_RULES` | Rename, update check IDs | To `DAST_CHECKS_TO_EXCLUDE` |
| `DAST_EXCLUDE_URLS` | Rename | To `DAST_SCOPE_EXCLUDE_URLS` |
| `DAST_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_FULL_SCAN_ENABLED` | Rename | To `DAST_FULL_SCAN` |
| `DAST_HTML_REPORT` | Remove | Not supported |
| `DAST_INCLUDE_ALPHA_VULNERABILITIES` | Remove | Not supported |
| `DAST_MARKDOWN_REPORT` | Remove | Not supported |
| `DAST_MASK_HTTP_HEADERS` | Remove | Not supported |
| `DAST_MAX_URLS_PER_VULNERABILITY` | Remove | Not supported |
| `DAST_ONLY_INCLUDE_RULES` | Rename, update check IDs | To `DAST_CHECKS_TO_RUN` |
| `DAST_PATHS` | None | Supported |
| `DAST_PATHS_FILE` | None | Supported |
| `DAST_PKCS12_CERTIFICATE_BASE64` | None | Supported |
| `DAST_PKCS12_PASSWORD` | None | Supported |
| `DAST_SKIP_TARGET_CHECK` | None | Supported |
| `DAST_SPIDER_MINS` | Change | To `DAST_CRAWL_TIMEOUT` using a duration. For example, instead of `5`, use `5m` |
| `DAST_SPIDER_START_AT_HOST` | Remove | Not supported |
| `DAST_TARGET_AVAILABILITY_TIMEOUT` | Change | To `DAST_TARGET_CHECK_TIMEOUT` using a duration. For example, instead of `60`, use `60s` |
| `DAST_USE_AJAX_SPIDER` | Remove | Not supported |
| `DAST_XML_REPORT` | Remove | Not supported |
| `DAST_WEBSITE` | Rename | To `DAST_TARGET_URL`<br/>GitLab Self-Managed: Upgrade your instance to version 17.0 or later before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
| `DAST_ZAP_CLI_OPTIONS` | Remove | Not supported |
| `DAST_ZAP_LOG_CONFIGURATION` | Remove | Not supported |
| `SECURE_ANALYZERS_PREFIX` | None | Supported |
|
---
stage: Application Security Testing
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
title: Migrating from the DAST proxy-based analyzer to DAST version 5
breadcrumbs:
- doc
- user
- application_security
- dast
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The [DAST proxy-based analyzer](proxy_based_to_browser_based_migration_guide.md) was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966) in GitLab 16.6 and removed in 17.0.
{{< /history >}}
[DAST version 5](browser/_index.md) replaces the proxy-based analyzer with a browser-based analyzer. This document serves as a guide to
migrate from the proxy-based analyzer to DAST version 5.
Follow this migration guide if all the following conditions apply:
1. You use GitLab DAST to run a DAST scan in a CI/CD pipeline.
1. The DAST CI/CD job is configured by including either of the DAST templates `DAST.gitlab-ci.yml` or `DAST.latest.gitlab-ci.yml`.
1. The CI/CD variable `DAST_VERSION` is not set or is set to `4` or less.
1. The CI/CD variable `DAST_BROWSER_SCAN` is not set or is set to `false`.
Migrate to DAST version 5 by reading the following sections and making the recommended changes.
## DAST analyzer versions
DAST comes in two major versions: 4 and 5.
Effective from GitLab 17.0 the DAST templates `DAST.gitlab-ci.yml` and `DAST.latest.gitlab-ci.yml` use DAST version 5 by default.
You can continue using DAST version 4, but you should do so only as an interim measure while migrating to DAST version 5. For details, see [Continuing to use the proxy-based analyzer](#continuing-to-use-the-proxy-based-analyzer).
Each DAST major version uses different analyzers by default:
- DAST version 4 uses the proxy-based analyzer.
- DAST version 5 uses the browser-based analyzer.
DAST version 5 uses a set of new CI/CD variables. Aliases have been created for the DAST version 4 variables' names.
Changes to make:
- To test your DAST scan using DAST version 5 in GitLab 16.11 and earlier, set the CI/CD variable `DAST_VERSION` to `5`.
## Continuing to use the proxy-based analyzer
You can use the proxy-based DAST analyzer until GitLab 18.0. Bugs and vulnerabilities in this legacy analyzer will not be fixed.
Changes to make:
- To continue using the proxy-based analyzer, set the CI/CD variable `DAST_VERSION` variable to `4`.
## Artifacts
GitLab 17.0 automatically publishes artifacts produced by DAST version 5 to the DAST CI job.
Changes to make:
- Remove `artifacts` from the CI job definition if you have overridden it to expose the file log, crawl graph, or authentication report.
- CI/CD variables `DAST_BROWSER_FILE_LOG_PATH` and `DAST_FILE_LOG_PATH` are no longer required.
## Authentication
The proxy-based analyzer and DAST version 5 both use the browser-based analyzer to authenticate. Upgrading
to DAST version 5 does not change how authentication works.
Changes to make:
- Rename authentication CI/CD variables, see variables with the `DAST_AUTH` prefix.
- If not already done, exclude the logout URL from the scan using `DAST_SCOPE_EXCLUDE_URLS`.
## Crawling
DAST version 5 crawls the target application in a browser to provide better crawl coverage. This may require
more resources to run than an equivalent proxy-based analyzer crawl.
Changes to make:
- Use `DAST_TARGET_URL` instead of `DAST_WEBSITE`.
- Use `DAST_CRAWL_TIMEOUT` instead of `DAST_SPIDER_MINS`.
- CI/CD variables `DAST_USE_AJAX_SPIDER`, `DAST_SPIDER_START_AT_HOST`, `DAST_ZAP_CLI_OPTIONS`
and `DAST_ZAP_LOG_CONFIGURATION` are no longer supported.
- Configure `DAST_PAGE_MAX_RESPONSE_SIZE_MB` if DAST should process response bodies larger than 10 MB.
- Consider providing more CPU resources to the GitLab Runner executing the DAST job.
## Scope
DAST version 5 provides more control over scope compared to the proxy-based analyzer.
Changes to make:
- Use `DAST_SCOPE_ALLOW_HOSTS` instead of `DAST_ALLOWED_HOSTS`.
- The domain of `DAST_TARGET_URL` is automatically added to `DAST_SCOPE_ALLOW_HOSTS`, consider adding domains for the
target application API and asset endpoints.
- Remove domains from the scan by adding them to `DAST_SCOPE_EXCLUDE_HOSTS` (except during authentication).
## Vulnerability checks
### Changes required
DAST version 5 uses vulnerability definitions built by GitLab, these do not map directly to proxy-based
analyzer definitions.
Changes to make:
- Use `DAST_CHECKS_TO_RUN` instead of `DAST_ONLY_INCLUDE_RULES`. Change the IDs used to GitLab DAST vulnerability check IDs.
- Use `DAST_CHECKS_TO_EXCLUDE` instead of `DAST_EXCLUDE_RULES`. Change the IDs used to GitLab DAST vulnerability check IDs.
- See [vulnerability check](browser/checks/_index.md) documentation for descriptions and IDs of GitLab DAST vulnerability checks.
- CI/CD variables `DAST_AGGREGATE_VULNERABILITIES` and `DAST_MAX_URLS_PER_VULNERABILITY` are no longer supported.
### Why migrating produces different vulnerabilities
Proxy-based scans and browser-based DAST version 5 scans do not produce the same results because they use a different set of vulnerability checks.
DAST version 5 does not have an equivalent for proxy-based checks that create too many false positives,
are not worth running because modern browsers don't allow the vulnerability to be exploited, or are no longer considered relevant.
DAST version 5 includes checks that proxy-based analyzer does not.
DAST version 5 scans provide better coverage of your application, so they may identify more vulnerabilities because more of your site is scanned.
### Coverage
One proxy-based active check is yet to be implemented in the browser-based DAST analyzer.
Migration of the remaining active check is proposed in
[epic 13411](https://gitlab.com/groups/gitlab-org/-/epics/13411). If you prefer to remain on DAST
version 4 until the last check is migrated, see [Continuing to use the proxy-based analyzer](#continuing-to-use-the-proxy-based-analyzer).
Remaining check:
- CWE-79: Cross-site Scripting (XSS)
## On-demand scans
On-demand scans runs a browser-based scan using [DAST version 5](https://gitlab.com/groups/gitlab-org/-/epics/11429) from GitLab 17.0.
## Troubleshooting
See the DAST version 5 [troubleshooting](browser/troubleshooting.md) documentation.
## Changes to CI/CD variables
The following table outlines migration actions required for each proxy-based analyzer CI/CD variable.
See [configuration](browser/configuration/_index.md) for more information on configuring DAST version 5.
| Proxy-based analyzer CI/CD variable | Required action | Notes |
|:-------------------------------------|:-------------------------|:-----------------------------------------------------------------------------------------|
| `DAST_ADVERTISE_SCAN` | Rename | To `DAST_REQUEST_ADVERTISE_SCAN` |
| `DAST_ALLOWED_HOSTS` | Rename | To `DAST_SCOPE_ALLOW_HOSTS` |
| `DAST_API_HOST_OVERRIDE` | Remove | Not supported |
| `DAST_API_SPECIFICATION` | Remove | Not supported |
| `DAST_AUTH_EXCLUDE_URLS` | Rename | To `DAST_SCOPE_EXCLUDE_URLS` |
| `DAST_AUTO_UPDATE_ADDONS` | Remove | Not supported |
| `DAST_BROWSER_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_DEBUG` | Remove | Not supported |
| `DAST_EXCLUDE_RULES` | Rename, update check IDs | To `DAST_CHECKS_TO_EXCLUDE` |
| `DAST_EXCLUDE_URLS` | Rename | To `DAST_SCOPE_EXCLUDE_URLS` |
| `DAST_FILE_LOG_PATH` | Remove | No longer required |
| `DAST_FULL_SCAN_ENABLED` | Rename | To `DAST_FULL_SCAN` |
| `DAST_HTML_REPORT` | Remove | Not supported |
| `DAST_INCLUDE_ALPHA_VULNERABILITIES` | Remove | Not supported |
| `DAST_MARKDOWN_REPORT` | Remove | Not supported |
| `DAST_MASK_HTTP_HEADERS` | Remove | Not supported |
| `DAST_MAX_URLS_PER_VULNERABILITY` | Remove | Not supported |
| `DAST_ONLY_INCLUDE_RULES` | Rename, update check IDs | To `DAST_CHECKS_TO_RUN` |
| `DAST_PATHS` | None | Supported |
| `DAST_PATHS_FILE` | None | Supported |
| `DAST_PKCS12_CERTIFICATE_BASE64` | None | Supported |
| `DAST_PKCS12_PASSWORD` | None | Supported |
| `DAST_SKIP_TARGET_CHECK` | None | Supported |
| `DAST_SPIDER_MINS` | Change | To `DAST_CRAWL_TIMEOUT` using a duration. For example, instead of `5`, use `5m` |
| `DAST_SPIDER_START_AT_HOST` | Remove | Not supported |
| `DAST_TARGET_AVAILABILITY_TIMEOUT` | Change | To `DAST_TARGET_CHECK_TIMEOUT` using a duration. For example, instead of `60`, use `60s` |
| `DAST_USE_AJAX_SPIDER` | Remove | Not supported |
| `DAST_XML_REPORT` | Remove | Not supported |
| `DAST_WEBSITE` | Rename | To `DAST_TARGET_URL`<br/>GitLab Self-Managed: Upgrade your instance to version 17.0 or later before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
| `DAST_ZAP_CLI_OPTIONS` | Remove | Not supported |
| `DAST_ZAP_LOG_CONFIGURATION` | Remove | Not supported |
| `SECURE_ANALYZERS_PREFIX` | None | Supported |
|
https://docs.gitlab.com/user/application_security/dast/troubleshooting
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/troubleshooting.md
|
2025-08-13
|
doc/user/application_security/dast/browser
|
[
"doc",
"user",
"application_security",
"dast",
"browser"
] |
troubleshooting.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Troubleshooting DAST scans
| null |
The following troubleshooting scenarios have been collected from customer support cases. If you
experience a problem not addressed here, or the information here does not fix your problem, create a
support ticket. For more details, see the [GitLab Support](https://about.gitlab.com/support/) page.
## When something goes wrong
When something goes wrong with a DAST scan, if you have a particular error message then check [known problems](#known-problems).
Otherwise, try to discover the problem by answering the following questions:
- [What is the expected outcome?](#what-is-the-expected-outcome)
- [Is the outcome achievable by a human?](#is-the-outcome-achievable-by-a-human)
- [Any reason why DAST would not work?](#any-reason-why-dast-would-not-work)
- [How does your application work?](#how-does-your-application-work)
- [What is DAST doing?](#what-is-dast-doing)
### What is the expected outcome?
Many users who encounter issues with a DAST scan have a good high-level idea of what they think the scanner should be doing. For example,
it's not scanning particular pages, or it's not selecting a button on the page.
As much as possible, try to isolate the problem to help narrow the search for a solution. For example, take the situation where DAST isn't scanning a particular page.
From where should DAST have found the page? What path did it take to get there? Were there elements on the referring page that DAST should have selected, but did not?
### Is the outcome achievable by a human?
DAST cannot scan an application if a human cannot manually traverse the application.
Knowing the outcome you expect, try to replicate it manually using a browser on your machine. For example:
- Open a new incognito/private browser window.
- Open Developer Tools. Keep an eye on the console for error messages.
- In Chrome: `View -> Developer -> Developer Tools`.
- In Firefox: `Tools -> Browser Tools -> Web Developer Tools`.
- If authenticating:
- Go to the `DAST_AUTH_URL`.
- Type in the `DAST_AUTH_USERNAME` in the `DAST_AUTH_USERNAME_FIELD`.
- Type in the `DAST_AUTH_PASSWORD` in the `DAST_AUTH_PASSWORD_FIELD`.
- Select the `DAST_AUTH_SUBMIT_FIELD`.
- Select links and fill in forms. Navigate to the pages that aren't scanning correctly.
- Observe how your application behaves. Notice if there is anything that might cause problems for an automated scanner.
### Any reason why DAST would not work?
DAST cannot scan correctly when:
- There is a CAPTCHA. Turn these off in the testing environment for the application being scanned.
- It does not have access to the target application. Ensure the GitLab Runner can access the application using the URLs used in the DAST configuration.
### How does your application work?
Understanding how your application works is vital to figuring out why a DAST scan isn't working. For example, the following situations
may require additional configuration settings.
- Is there a popup modal that hides elements?
- Does a loaded page change dramatically after a certain period of time?
- Is the application especially slow or fast to load?
- Is the target application jerky while loading?
- Does the application work differently based on the client's location?
- Is the application a single-page application?
- Does the application submit HTML forms, or does it use JavaScript and AJAX?
- Does the application use websockets?
- Does the application use a specific web framework?
- Does selecting buttons run JavaScript before continuing the form submit? Is it fast, slow?
- Is it possible DAST could be selecting or searching for elements before either the element or page is ready?
### What is DAST doing?
Logging remains the best way to understand what DAST is doing:
- [Browser-based analyzer logging](#browser-based-analyzer-logging), useful for understanding what the analyzer is doing.
- [Chromium DevTools logging](#chromium-devtools-logging), useful to inspect the communication between DAST and Chromium.
- [Chromium Logs](#chromium-logs), useful for logging errors when Chromium crashes unexpectedly.
## Browser-based analyzer logging
The analyzer log is one of the most useful tools to help diagnose problems with a scan. Different parts of the analyzer can be logged at different levels.
### Log message format
Log messages have the format `[time] [log level] [log module] [message] [additional properties]`.
For example, the following log entry has level `INFO`, is part of the `CRAWL` log module, has the message `Crawled path` and the additional properties `nav_id` and `path`.
```plaintext
2021-04-21T00:34:04.000 INF CRAWL Crawled path nav_id=0cc7fd path="LoadURL [https://my.site.com:8090]"
```
### Log destination
Logs are sent either to file or to console (the CI/CD job log). You can configure each destination to accept different logs using
the environment variables `DAST_LOG_CONFIG` for console logs and `DAST_LOG_FILE_CONFIG` for file logs.
For example:
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_BROWSER_SCAN: "true"
DAST_LOG_CONFIG: "auth:debug" # console log defaults to INFO level, logs AUTH module at DEBUG
DAST_LOG_FILE_CONFIG: "loglevel:debug,cache:warn" # file log defaults to DEBUG level, logs CACHE module at WARN
```
By default, the file log is a job artifact called `gl-dast-scan.log`.
To [configure this path](configuration/variables.md), modify the `DAST_LOG_FILE_PATH` CI/CD variable.
### Log levels
The log levels that can be configured are as follows:
| Log module | Component overview | More |
|-------------------------|--------------------------------------------------------------------------|----------------------------------|
| `TRACE` | Used for specific, often noisy inner workings of a feature. | |
| `DEBUG` | Describes the inner-workings of a feature. Used for diagnostic purposes. | |
| `INFO` | Describes the high level flow of the scan and the results. | Default level if none specified. |
| `WARN` | Describes an error situation where DAST recovers and continues the scan. | |
| `FATAL`/`ERROR`/`PANIC` | Describes unrecoverable errors prior to exit. | |
### Log modules
`LOGLEVEL` configures the default log level for the log destination. If any of the following modules are configured,
DAST uses the log level for that module in preference to the default log level.
The modules that can be configured for logging are as follows:
| Log module | Component overview |
|------------|---------------------------------------------------------------------------------------------------|
| `ACTIV` | Used for active attacks. |
| `AUTH` | Used for creating an authenticated scan. |
| `BPOOL` | The set of browsers that are leased out for crawling. |
| `BROWS` | Used for querying the state or page of the browser. |
| `CACHE` | Used for reporting on cache hit and miss for cached HTTP resources. |
| `CHROM` | Used to log Chrome DevTools messages. |
| `CONFG` | Used to log the analyzer configuration. |
| `CONTA` | Used for the container that collects parts of HTTP requests and responses from DevTools messages. |
| `CRAWL` | Used for the core crawler algorithm. |
| `CRWLG` | Used for the crawl graph generator. |
| `DATAB` | Used for persisting data to the internal database. |
| `LEASE` | Used to create browsers to add them to the browser pool. |
| `MAIN` | Used for the flow of the main event loop of the crawler. |
| `NAVDB` | Used for persistence mechanisms to store navigation entries. |
| `REGEX` | Used for recording performance statistics when running regular expressions. |
| `REPT` | Used for generating reports. |
| `STAT` | Used for general statistics while running the scan. |
| `VLDFN` | Used for loading and parsing vulnerability definitions. |
| `WEBGW` | Used to log messages sent to the target application when running active checks. |
| `SCOPE` | Used to log messages related to [scope management](configuration/customize_settings.md#managing-scope). |
### SECURE_LOG_LEVEL
{{< history >}}
- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/524632) in GitLab 17.11.
{{< /history >}}
As a simpler alternative to configuring log modules with `DAST_LOG_FILE_CONFIG`, you can set `SECURE_LOG_LEVEL`:
- To any of the [supported log levels](#log-levels).
When you do this, the specified level becomes the default log level in the log file for all modules.
- To `debug` or `trace` to enable the [auth report](configuration/authentication.md#configure-the-authentication-report).
- To `trace` to enable [DevTools logging](#chromium-devtools-logging).
For example:
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
SECURE_LOG_LEVEL: "trace"
# is equivalent to:
# DAST_LOG_FILE_CONFIG: "loglevel:trace"
# DAST_LOG_DEVTOOLS_CONFIG: "Default:messageAndBody,truncate:2000"
# DAST_AUTH_REPORT: "true"
```
Settings from `DAST_LOG_FILE_CONFIG`, `DAST_LOG_DEVTOOLS_CONFIG`, `DAST_AUTH_REPORT` override the settings from `SECURE_LOG_LEVEL`.
### Example - log crawled paths
Set the log module `CRAWL` to `DEBUG` to log navigation paths found during the crawl phase of the scan. This is useful for understanding
if DAST is crawling your target application correctly.
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_CONFIG: "crawl:debug"
```
For example, the following output shows that four anchor links we discovered during the crawl of the page at `https://example.com`.
```plaintext
2022-11-17T11:18:05.578 DBG CRAWL executing step nav_id=6ec647d8255c729160dd31cb124e6f89 path="LoadURL [https://example.com]" step=1
...
2022-11-17T11:18:11.900 DBG CRAWL found new navigations browser_id=2243909820020928961 nav_count=4 nav_id=6ec647d8255c729160dd31cb124e6f89 of=1 step=1
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page1.html]" nav=bd458cc1fc2d7c6fb984464b6d968866 parent_nav=6ec647d8255c729160dd31cb124e6f89
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page2.html]" nav=6dcb25f9f9ece3ee0071ac2e3166d8e6 parent_nav=6ec647d8255c729160dd31cb124e6f89
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page3.html]" nav=89efbb0c6154d6c6d85a63b61a7cdc6f parent_nav=6ec647d8255c729160dd31cb124e6f89
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page4.html]" nav=f29b4f4e0bdee70f5255de7fc080f04d parent_nav=6ec647d8255c729160dd31cb124e6f89
```
## Chromium DevTools logging
{{< alert type="warning" >}}
Logging DevTools messages is a security risk. The output contains secrets such as usernames, passwords and authentication tokens.
The output is uploaded to the GitLab server and may be visible in job logs.
{{< /alert >}}
The DAST Browser-based scanner orchestrates a Chromium browser using the [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/).
Logging DevTools messages helps provide transparency into what the browser is doing. For example, if selecting a button does not work, a DevTools message might show that the cause is a CORS error in a browser console log.
Logs that contain DevTools messages can be very large in size. For this reason, it should only be enabled on jobs with a short duration.
To log all DevTools messages, turn the `CHROM` log module to `trace` and configure logging levels. The following are examples of DevTools logs:
```plaintext
2022-12-05T06:27:24.280 TRC CHROM event received {"method":"Fetch.requestPaused","params":{"requestId":"interception-job-3.0","request":{"url":"http://auth-auto:8090/font-awesome.min.css","method":"GET","headers":{"Accept":"text/css,*/*;q=0.1","Referer":"http://auth-auto:8090/login.html","User-Agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/105.0.5195.102 Safari/537.36"},"initialPriority":"VeryHigh","referrerPolicy":"strict-origin-when-cross-origin"},"frameId":"A706468B01C2FFAA2EB6ED365FF95889","resourceType":"Stylesheet","networkId":"39.3"}} method=Fetch.requestPaused
2022-12-05T06:27:24.280 TRC CHROM request sent {"id":47,"method":"Fetch.continueRequest","params":{"requestId":"interception-job-3.0","headers":[{"name":"Accept","value":"text/css,*/*;q=0.1"},{"name":"Referer","value":"http://auth-auto:8090/login.html"},{"name":"User-Agent","value":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/105.0.5195.102 Safari/537.36"}]}} id=47 method=Fetch.continueRequest
2022-12-05T06:27:24.281 TRC CHROM response received {"id":47,"result":{}} id=47 method=Fetch.continueRequest
```
### Customizing DevTools log levels
Chrome DevTools requests, responses and events are namespaced by domain. DAST allows each domain and each domain with message to have different logging configuration.
The environment variable `DAST_LOG_DEVTOOLS_CONFIG` accepts a semi-colon separated list of logging configurations.
Logging configurations are declared using the structure `[domain/message]:[what-to-log][,truncate:[max-message-size]]`.
- `domain/message` references what is being logged.
- `Default` can be used as a value to represent all domains and messages.
- Can be a domain, for example, `Browser`, `CSS`, `Page`, `Network`.
- Can be a domain with a message, for example, `Network.responseReceived`.
- If multiple configurations apply, the most specific configuration is used.
- `what-to-log` references whether and what to log.
- `message` logs that a message was received and does not log the message content.
- `messageAndBody` logs the message with the message content. Recommended to be used with `truncate`.
- `suppress` does not log the message. Used to silence noisy domains and messages.
- `truncate` is an optional configuration to limit the size of the message printed.
### Example - log all DevTools messages
Used to log everything when you're not sure where to start.
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_FILE_CONFIG: "chrom:trace"
DAST_LOG_DEVTOOLS_CONFIG: "Default:messageAndBody,truncate:2000"
```
### Example - log HTTP messages
Useful for when a resource isn't loading correctly. HTTP message events are logged, as is the decision to continue or
fail the request. Any errors in the browser console are also logged.
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_FILE_CONFIG: "chrom:trace"
DAST_LOG_DEVTOOLS_CONFIG: "Default:suppress;Fetch:messageAndBody,truncate:2000;Network:messageAndBody,truncate:2000;Log:messageAndBody,truncate:2000;Console:messageAndBody,truncate:2000"
```
## Chromium logs
In the rare event that Chromium crashes, it can be helpful to write the Chromium process `STDOUT` and `STDERR` to log.
Setting the environment variable `DAST_LOG_BROWSER_OUTPUT` to `true` achieves this purpose.
DAST starts and stops many Chromium processes. DAST sends each process output to all log destinations with the log module `LEASE` and log level `INFO`.
For example:
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_BROWSER_OUTPUT: "true"
```
## Known problems
### Logs contain `response body exceeds allowed size`
By default DAST processes HTTP requests where the HTTP response body is 10 MB or less. Otherwise, DAST blocks the response
which can cause scans to fail. This constraint is intended to reduce memory consumption during a scan.
An example log is as follows, where DAST blocked the JavaScript file found at `https://example.com/large.js` as it's size is greater than the limit:
```plaintext
2022-12-05T06:28:43.093 WRN BROWS response body exceeds allowed size allowed_size_bytes=1000000 browser_id=752944257619431212 nav_id=ae23afe2acbce2c537657a9112926f1a of=1 request_id=interception-job-2.0 response_size_bytes=9333408 step=1 url=https://example.com/large.js
2022-12-05T06:28:58.104 WRN CONTA request failed, attempting to continue scan error=net::ERR_BLOCKED_BY_RESPONSE index=0 requestID=38.2 url=https://example.com/large.js
```
This can be changed using the configuration `DAST_PAGE_MAX_RESPONSE_SIZE_MB`. For example,
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_PAGE_MAX_RESPONSE_SIZE_MB: "25"
```
### Crawler doesn't reach expected pages
#### Try disabling the cache
If DAST incorrectly caches your application pages, it can lead to DAST being unable to properly crawl your application. If you see that some pages are unexpectedly not found by the crawler, try setting `DAST_USE_CACHE: "false"` variable to see if that helps. This can significantly decrease the performance of the scan. Make sure to only disable cache when absolutely necessary. If you have a subscription, [create a support ticket](https://about.gitlab.com/support/) to investigate why cache is preventing your website from being crawled.
#### Specifying target paths directly
The crawler typically begins at the defined target URL and attempts to find further pages by interacting with the site. However, there are two ways to specify paths directly for the crawler to start from:
- Using a sitemap.xml: [Sitemap](https://www.sitemaps.org/protocol.html) is a well defined protocol to specify the pages in a website. DAST's crawler looks for a sitemap.xml file at `<target URL>/sitemap.xml` and takes all specified URLs as a starting point for the crawler. [Sitemap Index](https://www.sitemaps.org/protocol.html#index) files are not supported.
- Using `DAST_TARGET_PATHS`: This configuration variable allows specifying input paths for the crawler. Example: `DAST_TARGET_PATHS: /,/page/1.html,/page/2.html`.
#### Make sure requests are not getting blocked
By default DAST only allows requests to the target URL's domain. If your website makes requests to domains other than the target's, use `DAST_SCOPE_ALLOW_HOSTS` to specify such hosts. Example: "example.com" makes an authentication request to "auth.example.com" to renew the authentication token. Because the domain is not allowed, the request gets blocked and the crawler fails to find new pages.
|
---
type: reference, howto
stage: Application Security Testing
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
title: Troubleshooting DAST scans
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
---
The following troubleshooting scenarios have been collected from customer support cases. If you
experience a problem not addressed here, or the information here does not fix your problem, create a
support ticket. For more details, see the [GitLab Support](https://about.gitlab.com/support/) page.
## When something goes wrong
When something goes wrong with a DAST scan, if you have a particular error message then check [known problems](#known-problems).
Otherwise, try to discover the problem by answering the following questions:
- [What is the expected outcome?](#what-is-the-expected-outcome)
- [Is the outcome achievable by a human?](#is-the-outcome-achievable-by-a-human)
- [Any reason why DAST would not work?](#any-reason-why-dast-would-not-work)
- [How does your application work?](#how-does-your-application-work)
- [What is DAST doing?](#what-is-dast-doing)
### What is the expected outcome?
Many users who encounter issues with a DAST scan have a good high-level idea of what they think the scanner should be doing. For example,
it's not scanning particular pages, or it's not selecting a button on the page.
As much as possible, try to isolate the problem to help narrow the search for a solution. For example, take the situation where DAST isn't scanning a particular page.
From where should DAST have found the page? What path did it take to get there? Were there elements on the referring page that DAST should have selected, but did not?
### Is the outcome achievable by a human?
DAST cannot scan an application if a human cannot manually traverse the application.
Knowing the outcome you expect, try to replicate it manually using a browser on your machine. For example:
- Open a new incognito/private browser window.
- Open Developer Tools. Keep an eye on the console for error messages.
- In Chrome: `View -> Developer -> Developer Tools`.
- In Firefox: `Tools -> Browser Tools -> Web Developer Tools`.
- If authenticating:
- Go to the `DAST_AUTH_URL`.
- Type in the `DAST_AUTH_USERNAME` in the `DAST_AUTH_USERNAME_FIELD`.
- Type in the `DAST_AUTH_PASSWORD` in the `DAST_AUTH_PASSWORD_FIELD`.
- Select the `DAST_AUTH_SUBMIT_FIELD`.
- Select links and fill in forms. Navigate to the pages that aren't scanning correctly.
- Observe how your application behaves. Notice if there is anything that might cause problems for an automated scanner.
### Any reason why DAST would not work?
DAST cannot scan correctly when:
- There is a CAPTCHA. Turn these off in the testing environment for the application being scanned.
- It does not have access to the target application. Ensure the GitLab Runner can access the application using the URLs used in the DAST configuration.
### How does your application work?
Understanding how your application works is vital to figuring out why a DAST scan isn't working. For example, the following situations
may require additional configuration settings.
- Is there a popup modal that hides elements?
- Does a loaded page change dramatically after a certain period of time?
- Is the application especially slow or fast to load?
- Is the target application jerky while loading?
- Does the application work differently based on the client's location?
- Is the application a single-page application?
- Does the application submit HTML forms, or does it use JavaScript and AJAX?
- Does the application use websockets?
- Does the application use a specific web framework?
- Does selecting buttons run JavaScript before continuing the form submit? Is it fast, slow?
- Is it possible DAST could be selecting or searching for elements before either the element or page is ready?
### What is DAST doing?
Logging remains the best way to understand what DAST is doing:
- [Browser-based analyzer logging](#browser-based-analyzer-logging), useful for understanding what the analyzer is doing.
- [Chromium DevTools logging](#chromium-devtools-logging), useful to inspect the communication between DAST and Chromium.
- [Chromium Logs](#chromium-logs), useful for logging errors when Chromium crashes unexpectedly.
## Browser-based analyzer logging
The analyzer log is one of the most useful tools to help diagnose problems with a scan. Different parts of the analyzer can be logged at different levels.
### Log message format
Log messages have the format `[time] [log level] [log module] [message] [additional properties]`.
For example, the following log entry has level `INFO`, is part of the `CRAWL` log module, has the message `Crawled path` and the additional properties `nav_id` and `path`.
```plaintext
2021-04-21T00:34:04.000 INF CRAWL Crawled path nav_id=0cc7fd path="LoadURL [https://my.site.com:8090]"
```
### Log destination
Logs are sent either to file or to console (the CI/CD job log). You can configure each destination to accept different logs using
the environment variables `DAST_LOG_CONFIG` for console logs and `DAST_LOG_FILE_CONFIG` for file logs.
For example:
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_BROWSER_SCAN: "true"
DAST_LOG_CONFIG: "auth:debug" # console log defaults to INFO level, logs AUTH module at DEBUG
DAST_LOG_FILE_CONFIG: "loglevel:debug,cache:warn" # file log defaults to DEBUG level, logs CACHE module at WARN
```
By default, the file log is a job artifact called `gl-dast-scan.log`.
To [configure this path](configuration/variables.md), modify the `DAST_LOG_FILE_PATH` CI/CD variable.
### Log levels
The log levels that can be configured are as follows:
| Log module | Component overview | More |
|-------------------------|--------------------------------------------------------------------------|----------------------------------|
| `TRACE` | Used for specific, often noisy inner workings of a feature. | |
| `DEBUG` | Describes the inner-workings of a feature. Used for diagnostic purposes. | |
| `INFO` | Describes the high level flow of the scan and the results. | Default level if none specified. |
| `WARN` | Describes an error situation where DAST recovers and continues the scan. | |
| `FATAL`/`ERROR`/`PANIC` | Describes unrecoverable errors prior to exit. | |
### Log modules
`LOGLEVEL` configures the default log level for the log destination. If any of the following modules are configured,
DAST uses the log level for that module in preference to the default log level.
The modules that can be configured for logging are as follows:
| Log module | Component overview |
|------------|---------------------------------------------------------------------------------------------------|
| `ACTIV` | Used for active attacks. |
| `AUTH` | Used for creating an authenticated scan. |
| `BPOOL` | The set of browsers that are leased out for crawling. |
| `BROWS` | Used for querying the state or page of the browser. |
| `CACHE` | Used for reporting on cache hit and miss for cached HTTP resources. |
| `CHROM` | Used to log Chrome DevTools messages. |
| `CONFG` | Used to log the analyzer configuration. |
| `CONTA` | Used for the container that collects parts of HTTP requests and responses from DevTools messages. |
| `CRAWL` | Used for the core crawler algorithm. |
| `CRWLG` | Used for the crawl graph generator. |
| `DATAB` | Used for persisting data to the internal database. |
| `LEASE` | Used to create browsers to add them to the browser pool. |
| `MAIN` | Used for the flow of the main event loop of the crawler. |
| `NAVDB` | Used for persistence mechanisms to store navigation entries. |
| `REGEX` | Used for recording performance statistics when running regular expressions. |
| `REPT` | Used for generating reports. |
| `STAT` | Used for general statistics while running the scan. |
| `VLDFN` | Used for loading and parsing vulnerability definitions. |
| `WEBGW` | Used to log messages sent to the target application when running active checks. |
| `SCOPE` | Used to log messages related to [scope management](configuration/customize_settings.md#managing-scope). |
### SECURE_LOG_LEVEL
{{< history >}}
- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/524632) in GitLab 17.11.
{{< /history >}}
As a simpler alternative to configuring log modules with `DAST_LOG_FILE_CONFIG`, you can set `SECURE_LOG_LEVEL`:
- To any of the [supported log levels](#log-levels).
When you do this, the specified level becomes the default log level in the log file for all modules.
- To `debug` or `trace` to enable the [auth report](configuration/authentication.md#configure-the-authentication-report).
- To `trace` to enable [DevTools logging](#chromium-devtools-logging).
For example:
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
SECURE_LOG_LEVEL: "trace"
# is equivalent to:
# DAST_LOG_FILE_CONFIG: "loglevel:trace"
# DAST_LOG_DEVTOOLS_CONFIG: "Default:messageAndBody,truncate:2000"
# DAST_AUTH_REPORT: "true"
```
Settings from `DAST_LOG_FILE_CONFIG`, `DAST_LOG_DEVTOOLS_CONFIG`, `DAST_AUTH_REPORT` override the settings from `SECURE_LOG_LEVEL`.
### Example - log crawled paths
Set the log module `CRAWL` to `DEBUG` to log navigation paths found during the crawl phase of the scan. This is useful for understanding
if DAST is crawling your target application correctly.
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_CONFIG: "crawl:debug"
```
For example, the following output shows that four anchor links we discovered during the crawl of the page at `https://example.com`.
```plaintext
2022-11-17T11:18:05.578 DBG CRAWL executing step nav_id=6ec647d8255c729160dd31cb124e6f89 path="LoadURL [https://example.com]" step=1
...
2022-11-17T11:18:11.900 DBG CRAWL found new navigations browser_id=2243909820020928961 nav_count=4 nav_id=6ec647d8255c729160dd31cb124e6f89 of=1 step=1
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page1.html]" nav=bd458cc1fc2d7c6fb984464b6d968866 parent_nav=6ec647d8255c729160dd31cb124e6f89
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page2.html]" nav=6dcb25f9f9ece3ee0071ac2e3166d8e6 parent_nav=6ec647d8255c729160dd31cb124e6f89
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page3.html]" nav=89efbb0c6154d6c6d85a63b61a7cdc6f parent_nav=6ec647d8255c729160dd31cb124e6f89
2022-11-17T11:18:11.901 DBG CRAWL adding navigation action="LeftClick [a href=/page4.html]" nav=f29b4f4e0bdee70f5255de7fc080f04d parent_nav=6ec647d8255c729160dd31cb124e6f89
```
## Chromium DevTools logging
{{< alert type="warning" >}}
Logging DevTools messages is a security risk. The output contains secrets such as usernames, passwords and authentication tokens.
The output is uploaded to the GitLab server and may be visible in job logs.
{{< /alert >}}
The DAST Browser-based scanner orchestrates a Chromium browser using the [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/).
Logging DevTools messages helps provide transparency into what the browser is doing. For example, if selecting a button does not work, a DevTools message might show that the cause is a CORS error in a browser console log.
Logs that contain DevTools messages can be very large in size. For this reason, it should only be enabled on jobs with a short duration.
To log all DevTools messages, turn the `CHROM` log module to `trace` and configure logging levels. The following are examples of DevTools logs:
```plaintext
2022-12-05T06:27:24.280 TRC CHROM event received {"method":"Fetch.requestPaused","params":{"requestId":"interception-job-3.0","request":{"url":"http://auth-auto:8090/font-awesome.min.css","method":"GET","headers":{"Accept":"text/css,*/*;q=0.1","Referer":"http://auth-auto:8090/login.html","User-Agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/105.0.5195.102 Safari/537.36"},"initialPriority":"VeryHigh","referrerPolicy":"strict-origin-when-cross-origin"},"frameId":"A706468B01C2FFAA2EB6ED365FF95889","resourceType":"Stylesheet","networkId":"39.3"}} method=Fetch.requestPaused
2022-12-05T06:27:24.280 TRC CHROM request sent {"id":47,"method":"Fetch.continueRequest","params":{"requestId":"interception-job-3.0","headers":[{"name":"Accept","value":"text/css,*/*;q=0.1"},{"name":"Referer","value":"http://auth-auto:8090/login.html"},{"name":"User-Agent","value":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/105.0.5195.102 Safari/537.36"}]}} id=47 method=Fetch.continueRequest
2022-12-05T06:27:24.281 TRC CHROM response received {"id":47,"result":{}} id=47 method=Fetch.continueRequest
```
### Customizing DevTools log levels
Chrome DevTools requests, responses and events are namespaced by domain. DAST allows each domain and each domain with message to have different logging configuration.
The environment variable `DAST_LOG_DEVTOOLS_CONFIG` accepts a semi-colon separated list of logging configurations.
Logging configurations are declared using the structure `[domain/message]:[what-to-log][,truncate:[max-message-size]]`.
- `domain/message` references what is being logged.
- `Default` can be used as a value to represent all domains and messages.
- Can be a domain, for example, `Browser`, `CSS`, `Page`, `Network`.
- Can be a domain with a message, for example, `Network.responseReceived`.
- If multiple configurations apply, the most specific configuration is used.
- `what-to-log` references whether and what to log.
- `message` logs that a message was received and does not log the message content.
- `messageAndBody` logs the message with the message content. Recommended to be used with `truncate`.
- `suppress` does not log the message. Used to silence noisy domains and messages.
- `truncate` is an optional configuration to limit the size of the message printed.
### Example - log all DevTools messages
Used to log everything when you're not sure where to start.
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_FILE_CONFIG: "chrom:trace"
DAST_LOG_DEVTOOLS_CONFIG: "Default:messageAndBody,truncate:2000"
```
### Example - log HTTP messages
Useful for when a resource isn't loading correctly. HTTP message events are logged, as is the decision to continue or
fail the request. Any errors in the browser console are also logged.
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_FILE_CONFIG: "chrom:trace"
DAST_LOG_DEVTOOLS_CONFIG: "Default:suppress;Fetch:messageAndBody,truncate:2000;Network:messageAndBody,truncate:2000;Log:messageAndBody,truncate:2000;Console:messageAndBody,truncate:2000"
```
## Chromium logs
In the rare event that Chromium crashes, it can be helpful to write the Chromium process `STDOUT` and `STDERR` to log.
Setting the environment variable `DAST_LOG_BROWSER_OUTPUT` to `true` achieves this purpose.
DAST starts and stops many Chromium processes. DAST sends each process output to all log destinations with the log module `LEASE` and log level `INFO`.
For example:
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_LOG_BROWSER_OUTPUT: "true"
```
## Known problems
### Logs contain `response body exceeds allowed size`
By default DAST processes HTTP requests where the HTTP response body is 10 MB or less. Otherwise, DAST blocks the response
which can cause scans to fail. This constraint is intended to reduce memory consumption during a scan.
An example log is as follows, where DAST blocked the JavaScript file found at `https://example.com/large.js` as it's size is greater than the limit:
```plaintext
2022-12-05T06:28:43.093 WRN BROWS response body exceeds allowed size allowed_size_bytes=1000000 browser_id=752944257619431212 nav_id=ae23afe2acbce2c537657a9112926f1a of=1 request_id=interception-job-2.0 response_size_bytes=9333408 step=1 url=https://example.com/large.js
2022-12-05T06:28:58.104 WRN CONTA request failed, attempting to continue scan error=net::ERR_BLOCKED_BY_RESPONSE index=0 requestID=38.2 url=https://example.com/large.js
```
This can be changed using the configuration `DAST_PAGE_MAX_RESPONSE_SIZE_MB`. For example,
```yaml
include:
- template: DAST.gitlab-ci.yml
dast:
variables:
DAST_PAGE_MAX_RESPONSE_SIZE_MB: "25"
```
### Crawler doesn't reach expected pages
#### Try disabling the cache
If DAST incorrectly caches your application pages, it can lead to DAST being unable to properly crawl your application. If you see that some pages are unexpectedly not found by the crawler, try setting `DAST_USE_CACHE: "false"` variable to see if that helps. This can significantly decrease the performance of the scan. Make sure to only disable cache when absolutely necessary. If you have a subscription, [create a support ticket](https://about.gitlab.com/support/) to investigate why cache is preventing your website from being crawled.
#### Specifying target paths directly
The crawler typically begins at the defined target URL and attempts to find further pages by interacting with the site. However, there are two ways to specify paths directly for the crawler to start from:
- Using a sitemap.xml: [Sitemap](https://www.sitemaps.org/protocol.html) is a well defined protocol to specify the pages in a website. DAST's crawler looks for a sitemap.xml file at `<target URL>/sitemap.xml` and takes all specified URLs as a starting point for the crawler. [Sitemap Index](https://www.sitemaps.org/protocol.html#index) files are not supported.
- Using `DAST_TARGET_PATHS`: This configuration variable allows specifying input paths for the crawler. Example: `DAST_TARGET_PATHS: /,/page/1.html,/page/2.html`.
#### Make sure requests are not getting blocked
By default DAST only allows requests to the target URL's domain. If your website makes requests to domains other than the target's, use `DAST_SCOPE_ALLOW_HOSTS` to specify such hosts. Example: "example.com" makes an authentication request to "auth.example.com" to renew the authentication token. Because the domain is not allowed, the request gets blocked and the crawler fails to find new pages.
|
https://docs.gitlab.com/user/application_security/dast/application_deployment_options
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/application_deployment_options.md
|
2025-08-13
|
doc/user/application_security/dast/browser
|
[
"doc",
"user",
"application_security",
"dast",
"browser"
] |
application_deployment_options.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Application deployment options
| null |
DAST requires a deployed application to be available to scan.
Depending on the complexity of the target application, there are a few options as to how to deploy and configure
the DAST template. A set of example applications have been provided with their configurations in the
[DAST demonstrations](https://gitlab.com/gitlab-org/security-products/demos/dast/) project.
## Review apps
Review apps are the most involved method of deploying your DAST target application. To assist in the process,
GitLab created a review app deployment using Google Kubernetes Engine (GKE). This example can be found in the
[Review apps - GKE](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke) project, plus detailed
instructions to configure review apps for DAST in the [README](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke/-/blob/master/README.md).
## Docker Services
If your application uses Docker containers you have another option for deploying and scanning with DAST.
After your Docker build job completes and your image is added to your container registry, you can use the image as a
[service](../../../../ci/services/_index.md).
By using service definitions in your `.gitlab-ci.yml`, you can scan services with the DAST analyzer.
When adding a `services` section to the job, the `alias` is used to define the hostname that can be used to access the service. In the following example, the `alias: yourapp` portion of the `dast` job definition means that the URL to the deployed application uses `yourapp` as the hostname (`https://yourapp/`).
```yaml
stages:
- build
- dast
include:
- template: DAST.gitlab-ci.yml
# Deploys the container to the GitLab container registry
deploy:
services:
- name: docker:dind
alias: dind
image: docker:20.10.16
stage: build
script:
- docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
- docker pull $CI_REGISTRY_IMAGE:latest || true
- docker build --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:latest .
- docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
- docker push $CI_REGISTRY_IMAGE:latest
dast:
services: # use services to link your app container to the dast job
- name: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
alias: yourapp
variables:
DAST_TARGET_URL: https://yourapp
DAST_FULL_SCAN: "true" # do a full scan
DAST_BROWSER_SCAN: "true" # use the browser-based GitLab DAST crawler
```
Most applications depend on multiple services such as databases or caching services. By default, services defined in the services fields cannot communicate
with each another. To allow communication between services, enable the `FF_NETWORK_PER_BUILD` [feature flag](https://docs.gitlab.com/runner/configuration/feature-flags.html#available-feature-flags).
```yaml
variables:
FF_NETWORK_PER_BUILD: "true" # enable network per build so all services can communicate on the same network
services: # use services to link the container to the dast job
- name: mongo:latest
alias: mongo
- name: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
alias: yourapp
```
|
---
type: reference, howto
stage: Application Security Testing
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
title: Application deployment options
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
---
DAST requires a deployed application to be available to scan.
Depending on the complexity of the target application, there are a few options as to how to deploy and configure
the DAST template. A set of example applications have been provided with their configurations in the
[DAST demonstrations](https://gitlab.com/gitlab-org/security-products/demos/dast/) project.
## Review apps
Review apps are the most involved method of deploying your DAST target application. To assist in the process,
GitLab created a review app deployment using Google Kubernetes Engine (GKE). This example can be found in the
[Review apps - GKE](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke) project, plus detailed
instructions to configure review apps for DAST in the [README](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke/-/blob/master/README.md).
## Docker Services
If your application uses Docker containers you have another option for deploying and scanning with DAST.
After your Docker build job completes and your image is added to your container registry, you can use the image as a
[service](../../../../ci/services/_index.md).
By using service definitions in your `.gitlab-ci.yml`, you can scan services with the DAST analyzer.
When adding a `services` section to the job, the `alias` is used to define the hostname that can be used to access the service. In the following example, the `alias: yourapp` portion of the `dast` job definition means that the URL to the deployed application uses `yourapp` as the hostname (`https://yourapp/`).
```yaml
stages:
- build
- dast
include:
- template: DAST.gitlab-ci.yml
# Deploys the container to the GitLab container registry
deploy:
services:
- name: docker:dind
alias: dind
image: docker:20.10.16
stage: build
script:
- docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
- docker pull $CI_REGISTRY_IMAGE:latest || true
- docker build --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:latest .
- docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
- docker push $CI_REGISTRY_IMAGE:latest
dast:
services: # use services to link your app container to the dast job
- name: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
alias: yourapp
variables:
DAST_TARGET_URL: https://yourapp
DAST_FULL_SCAN: "true" # do a full scan
DAST_BROWSER_SCAN: "true" # use the browser-based GitLab DAST crawler
```
Most applications depend on multiple services such as databases or caching services. By default, services defined in the services fields cannot communicate
with each another. To allow communication between services, enable the `FF_NETWORK_PER_BUILD` [feature flag](https://docs.gitlab.com/runner/configuration/feature-flags.html#available-feature-flags).
```yaml
variables:
FF_NETWORK_PER_BUILD: "true" # enable network per build so all services can communicate on the same network
services: # use services to link the container to the dast job
- name: mongo:latest
alias: mongo
- name: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
alias: yourapp
```
|
https://docs.gitlab.com/user/application_security/dast/browser
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/_index.md
|
2025-08-13
|
doc/user/application_security/dast/browser
|
[
"doc",
"user",
"application_security",
"dast",
"browser"
] |
_index.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
DAST browser-based analyzer
| null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Generally available](https://gitlab.com/groups/gitlab-org/-/epics/9023) in GitLab 15.7 (GitLab DAST v3.0.50).
{{< /history >}}
{{< alert type="warning" >}}
The DAST version 4 browser-based analyzer is replaced by DAST version 5 in GitLab 17.0.
For instructions on how to migrate to DAST version 5, see the [migration guide](../browser_based_4_to_5_migration_guide.md).
{{< /alert >}}
Browser-based DAST helps you identify security weaknesses (CWEs) in your web applications. After you
deploy your web application, it becomes exposed to new types of attacks, many of which cannot be
detected prior to deployment. For example, misconfigurations of your application server or incorrect
assumptions about security controls may not be visible from the source code, but they can be
detected with browser-based DAST.
Dynamic Application Security Testing (DAST) examines applications for vulnerabilities like these in
deployed environments.
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For an overview, see [Dynamic Application Security Testing (DAST) - Advanced Security Testing](https://www.youtube.com/watch?v=nbeDUoLZJTo).
{{< alert type="warning" >}}
Do not run DAST scans against a production server. Not only can it perform any function that a
user can, such as clicking buttons or submitting forms, but it may also trigger bugs, leading to
modification or loss of production data. Only run DAST scans against a test server.
{{< /alert >}}
The DAST browser-based analyzer was built by GitLab to scan modern-day web applications for
vulnerabilities. Scans run in a browser to optimize testing applications heavily dependent on
JavaScript, such as single-page applications. See
[how DAST scans an application](#how-dast-scans-an-application) for more information.
To add the analyzer to your CI/CD pipeline, see [enabling the analyzer](configuration/enabling_the_analyzer.md).
## Getting started
If you're new to DAST, get started by enabling it for a project.
Prerequisites:
- You have a [GitLab Runner](../../../../ci/runners/_index.md) with the
[`docker` executor](https://docs.gitlab.com/runner/executors/docker.html) on Linux/amd64.
- You have a deployed target application. For more details, see the [deployment options](application_deployment_options.md).
- The `dast` stage is added to the CI/CD pipeline definition, after the `deploy` stage. For example:
```yaml
stages:
- build
- test
- deploy
- dast
```
- You have a network connection between the runner and your target application.
How you connect depends on your DAST configuration:
- If `DAST_TARGET_URL` and `DAST_AUTH_URL` specify port numbers, use those ports.
- If ports are not specified, use the standard port numbers for HTTP and HTTPS.
You might need to open both an HTTP and HTTPS port. For example, if the target URL uses HTTP, but the application links to resources using HTTPS. Always test your connection when you configure a scan.
To enable DAST in a project:
- [Add a DAST job to you CI/CD configuration](configuration/enabling_the_analyzer.md#create-a-dast-cicd-job).
## Understanding the results
You can review vulnerabilities in a pipeline:
1. On the left sidebar, select **Search or go to** and find your project.
1. On the left sidebar, select **Build > Pipelines**.
1. Select the pipeline.
1. Select the **Security** tab.
1. Select a vulnerability to view its details, including:
- Status: Indicates whether the vulnerability has been triaged or resolved.
- Description: Explains the cause of the vulnerability, its potential impact, and recommended remediation steps.
- Severity: Categorized into six levels based on impact.
[Learn more about severity levels](../../vulnerabilities/severities.md).
- Scanner: Identifies which analyzer detected the vulnerability.
- Method: Establishes the vulnerable server interaction type.
- URL: Shows the location of the vulnerability.
- Evidence: Describes test case to prove the presence of a given vulnerability.
- Identifiers: A list of references used to classify the vulnerability, such as CWE identifiers.
You can also download the security scan results:
- In the pipeline's **Security** tab, select **Download results**.
For more details, see [Pipeline security report](../../vulnerability_report/pipeline.md).
{{< alert type="note" >}}
Findings are generated on feature branches. When they are merged into the default branch, they become vulnerabilities. This distinction is important when evaluating your security posture.
{{< /alert >}}
## Optimization
For information about configuring DAST for a specific application or environment, see the [configuration options](configuration/_index.md).
## Roll out
After you configure DAST for a single project, you can extend the configuration to other projects:
- Take care if your pipeline is configured to deploy to the same web server in each run. Running a DAST scan while a server is being updated leads to inaccurate and non-deterministic results.
- Configure runners to use the [always pull policy](https://docs.gitlab.com/runner/executors/docker.html#using-the-always-pull-policy) to run the latest versions of the analyzers.
- By default, DAST downloads all artifacts defined by previous jobs in the pipeline. If
your DAST job does not rely on `environment_url.txt` to define the URL under test or any other files created
in previous jobs, you shouldn't download artifacts. To avoid downloading
artifacts, extend the analyzer CI/CD job to specify no dependencies. For example, for the DAST proxy-based analyzer add the following to your `.gitlab-ci.yml` file:
```yaml
dast:
dependencies: []
```
## How DAST scans an application
A scan performs the following steps:
1. [Authenticate](configuration/authentication.md), if configured.
1. [Crawl](#crawling-an-application) the target application to discover the surface area of the application by performing user actions such as following links, clicking buttons, and filling out forms.
1. [Passive scan](#passive-scans) to search for vulnerabilities in HTTP messages and pages discovered while crawling.
1. [Active scan](#active-scans) to search for vulnerabilities by injecting payloads into HTTP requests recorded during the crawl phase.
### Crawling an application
A "navigation" is an action a user might take on a page, such as clicking buttons, clicking anchor links, opening menu items, or filling out forms.
A "navigation path" is a sequence of navigation actions representing how a user might traverse an application.
DAST discovers the surface area of an application by crawling pages and content and identifying navigation paths.
Crawling is initialized with a navigation path containing one navigation that loads the target application URL in a specially-instrumented Chromium browser.
DAST then crawls navigation paths until all have been crawled.
To crawl a navigation path, DAST opens a browser window and instructs it to perform all the navigation actions in the navigation path.
When the browser has finished loading the result of the final action, DAST inspects the page for actions a user might take,
creates a new navigation for each found, and adds them to the navigation path to form new navigation paths. For example:
1. DAST processes navigation path `LoadURL[https://example.com]`.
1. DAST finds two user actions, `LeftClick[class=menu]` and `LeftClick[id=users]`.
1. DAST creates two new navigation paths, `LoadURL[https://example.com] -> LeftClick[class=menu]` and `LoadURL[https://example.com] -> LeftClick[id=users]`.
1. Crawling begins on the two new navigation paths.
It's common for an HTML element to exist in multiple places in an application, such as a menu visible on every page.
Duplicate elements can cause crawlers to crawl the same pages again or become stuck in a loop.
DAST uses an element uniqueness calculation based on HTML attributes to discard new navigation actions it has previously crawled.
### Passive scans
Passive scans check for vulnerabilities in the pages discovered during the crawl phase of the scan.
Passive scans attempt to interact with a site in the same way as a normal user, including by performing destructive actions like deleting data.
However, passive scans do not simulate adversarial behavior.
Passive scans are enabled by default.
The checks search HTTP messages, cookies, storage events, console events, and DOM for vulnerabilities.
Examples of passive checks include searching for exposed credit cards, exposed secret tokens, missing content security policies, and redirection to untrusted locations.
See [checks](checks/_index.md) for more information about individual checks.
### Active scans
Active scans check for vulnerabilities by injecting attack payloads into HTTP requests recorded during the crawl phase of the scan.
Active scans are disabled by default because they simulate adversarial behavior.
DAST analyzes each recorded HTTP request for injection locations, such as query values, header values, cookie values, form posts, and JSON string values.
Attack payloads are injected into the injection location, forming a new request.
DAST sends the request to the target application and uses the HTTP response to determine attack success.
Active scans run two types of active check:
- A match response attack analyzes the response content to determine attack success. For example, if an attack attempts to read the system password file, a finding is created when the response body contains evidence of the password file.
- A timing attack uses the response time to determine attack success. For example, if an attack attempts to force the target application to sleep, a finding is created when the application takes longer to respond than the sleep time. Timing attacks are repeated multiple times with different attack payloads to minimize false positives.
A simplified timing attack works as follows:
1. The crawl phase records the HTTP request `https://example.com?search=people`.
1. DAST analyzes the URL and finds a URL parameter injection location `https://example.com?search=[INJECT]`.
1. The active check defines a payload, `sleep 10`, that attempts to get a Linux host to sleep.
1. DAST send a new HTTP request to the target application with the injected payload `https://example.com?search=sleep%2010`.
1. The target application is vulnerable if it executes the query parameter value as a system command without validation, for example, `system(params[:search])`
1. DAST creates a finding if the response time takes longer than 10 seconds.
|
---
type: reference, howto
stage: Application Security Testing
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
title: DAST browser-based analyzer
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
---
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Generally available](https://gitlab.com/groups/gitlab-org/-/epics/9023) in GitLab 15.7 (GitLab DAST v3.0.50).
{{< /history >}}
{{< alert type="warning" >}}
The DAST version 4 browser-based analyzer is replaced by DAST version 5 in GitLab 17.0.
For instructions on how to migrate to DAST version 5, see the [migration guide](../browser_based_4_to_5_migration_guide.md).
{{< /alert >}}
Browser-based DAST helps you identify security weaknesses (CWEs) in your web applications. After you
deploy your web application, it becomes exposed to new types of attacks, many of which cannot be
detected prior to deployment. For example, misconfigurations of your application server or incorrect
assumptions about security controls may not be visible from the source code, but they can be
detected with browser-based DAST.
Dynamic Application Security Testing (DAST) examines applications for vulnerabilities like these in
deployed environments.
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For an overview, see [Dynamic Application Security Testing (DAST) - Advanced Security Testing](https://www.youtube.com/watch?v=nbeDUoLZJTo).
{{< alert type="warning" >}}
Do not run DAST scans against a production server. Not only can it perform any function that a
user can, such as clicking buttons or submitting forms, but it may also trigger bugs, leading to
modification or loss of production data. Only run DAST scans against a test server.
{{< /alert >}}
The DAST browser-based analyzer was built by GitLab to scan modern-day web applications for
vulnerabilities. Scans run in a browser to optimize testing applications heavily dependent on
JavaScript, such as single-page applications. See
[how DAST scans an application](#how-dast-scans-an-application) for more information.
To add the analyzer to your CI/CD pipeline, see [enabling the analyzer](configuration/enabling_the_analyzer.md).
## Getting started
If you're new to DAST, get started by enabling it for a project.
Prerequisites:
- You have a [GitLab Runner](../../../../ci/runners/_index.md) with the
[`docker` executor](https://docs.gitlab.com/runner/executors/docker.html) on Linux/amd64.
- You have a deployed target application. For more details, see the [deployment options](application_deployment_options.md).
- The `dast` stage is added to the CI/CD pipeline definition, after the `deploy` stage. For example:
```yaml
stages:
- build
- test
- deploy
- dast
```
- You have a network connection between the runner and your target application.
How you connect depends on your DAST configuration:
- If `DAST_TARGET_URL` and `DAST_AUTH_URL` specify port numbers, use those ports.
- If ports are not specified, use the standard port numbers for HTTP and HTTPS.
You might need to open both an HTTP and HTTPS port. For example, if the target URL uses HTTP, but the application links to resources using HTTPS. Always test your connection when you configure a scan.
To enable DAST in a project:
- [Add a DAST job to you CI/CD configuration](configuration/enabling_the_analyzer.md#create-a-dast-cicd-job).
## Understanding the results
You can review vulnerabilities in a pipeline:
1. On the left sidebar, select **Search or go to** and find your project.
1. On the left sidebar, select **Build > Pipelines**.
1. Select the pipeline.
1. Select the **Security** tab.
1. Select a vulnerability to view its details, including:
- Status: Indicates whether the vulnerability has been triaged or resolved.
- Description: Explains the cause of the vulnerability, its potential impact, and recommended remediation steps.
- Severity: Categorized into six levels based on impact.
[Learn more about severity levels](../../vulnerabilities/severities.md).
- Scanner: Identifies which analyzer detected the vulnerability.
- Method: Establishes the vulnerable server interaction type.
- URL: Shows the location of the vulnerability.
- Evidence: Describes test case to prove the presence of a given vulnerability.
- Identifiers: A list of references used to classify the vulnerability, such as CWE identifiers.
You can also download the security scan results:
- In the pipeline's **Security** tab, select **Download results**.
For more details, see [Pipeline security report](../../vulnerability_report/pipeline.md).
{{< alert type="note" >}}
Findings are generated on feature branches. When they are merged into the default branch, they become vulnerabilities. This distinction is important when evaluating your security posture.
{{< /alert >}}
## Optimization
For information about configuring DAST for a specific application or environment, see the [configuration options](configuration/_index.md).
## Roll out
After you configure DAST for a single project, you can extend the configuration to other projects:
- Take care if your pipeline is configured to deploy to the same web server in each run. Running a DAST scan while a server is being updated leads to inaccurate and non-deterministic results.
- Configure runners to use the [always pull policy](https://docs.gitlab.com/runner/executors/docker.html#using-the-always-pull-policy) to run the latest versions of the analyzers.
- By default, DAST downloads all artifacts defined by previous jobs in the pipeline. If
your DAST job does not rely on `environment_url.txt` to define the URL under test or any other files created
in previous jobs, you shouldn't download artifacts. To avoid downloading
artifacts, extend the analyzer CI/CD job to specify no dependencies. For example, for the DAST proxy-based analyzer add the following to your `.gitlab-ci.yml` file:
```yaml
dast:
dependencies: []
```
## How DAST scans an application
A scan performs the following steps:
1. [Authenticate](configuration/authentication.md), if configured.
1. [Crawl](#crawling-an-application) the target application to discover the surface area of the application by performing user actions such as following links, clicking buttons, and filling out forms.
1. [Passive scan](#passive-scans) to search for vulnerabilities in HTTP messages and pages discovered while crawling.
1. [Active scan](#active-scans) to search for vulnerabilities by injecting payloads into HTTP requests recorded during the crawl phase.
### Crawling an application
A "navigation" is an action a user might take on a page, such as clicking buttons, clicking anchor links, opening menu items, or filling out forms.
A "navigation path" is a sequence of navigation actions representing how a user might traverse an application.
DAST discovers the surface area of an application by crawling pages and content and identifying navigation paths.
Crawling is initialized with a navigation path containing one navigation that loads the target application URL in a specially-instrumented Chromium browser.
DAST then crawls navigation paths until all have been crawled.
To crawl a navigation path, DAST opens a browser window and instructs it to perform all the navigation actions in the navigation path.
When the browser has finished loading the result of the final action, DAST inspects the page for actions a user might take,
creates a new navigation for each found, and adds them to the navigation path to form new navigation paths. For example:
1. DAST processes navigation path `LoadURL[https://example.com]`.
1. DAST finds two user actions, `LeftClick[class=menu]` and `LeftClick[id=users]`.
1. DAST creates two new navigation paths, `LoadURL[https://example.com] -> LeftClick[class=menu]` and `LoadURL[https://example.com] -> LeftClick[id=users]`.
1. Crawling begins on the two new navigation paths.
It's common for an HTML element to exist in multiple places in an application, such as a menu visible on every page.
Duplicate elements can cause crawlers to crawl the same pages again or become stuck in a loop.
DAST uses an element uniqueness calculation based on HTML attributes to discard new navigation actions it has previously crawled.
### Passive scans
Passive scans check for vulnerabilities in the pages discovered during the crawl phase of the scan.
Passive scans attempt to interact with a site in the same way as a normal user, including by performing destructive actions like deleting data.
However, passive scans do not simulate adversarial behavior.
Passive scans are enabled by default.
The checks search HTTP messages, cookies, storage events, console events, and DOM for vulnerabilities.
Examples of passive checks include searching for exposed credit cards, exposed secret tokens, missing content security policies, and redirection to untrusted locations.
See [checks](checks/_index.md) for more information about individual checks.
### Active scans
Active scans check for vulnerabilities by injecting attack payloads into HTTP requests recorded during the crawl phase of the scan.
Active scans are disabled by default because they simulate adversarial behavior.
DAST analyzes each recorded HTTP request for injection locations, such as query values, header values, cookie values, form posts, and JSON string values.
Attack payloads are injected into the injection location, forming a new request.
DAST sends the request to the target application and uses the HTTP response to determine attack success.
Active scans run two types of active check:
- A match response attack analyzes the response content to determine attack success. For example, if an attack attempts to read the system password file, a finding is created when the response body contains evidence of the password file.
- A timing attack uses the response time to determine attack success. For example, if an attack attempts to force the target application to sleep, a finding is created when the application takes longer to respond than the sleep time. Timing attacks are repeated multiple times with different attack payloads to minimize false positives.
A simplified timing attack works as follows:
1. The crawl phase records the HTTP request `https://example.com?search=people`.
1. DAST analyzes the URL and finds a URL parameter injection location `https://example.com?search=[INJECT]`.
1. The active check defines a payload, `sleep 10`, that attempts to get a Linux host to sleep.
1. DAST send a new HTTP request to the target application with the injected payload `https://example.com?search=sleep%2010`.
1. The target application is vulnerable if it executes the query parameter value as a system command without validation, for example, `system(params[:search])`
1. DAST creates a finding if the response time takes longer than 10 seconds.
|
https://docs.gitlab.com/user/application_security/dast/browser/798.56
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.56.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.56.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GitLab personal access token
| null |
## Description
The response body contains content that matches the pattern of a GitLab personal access token was identified. Personal access tokens can be used to access GitLab services as the user who created them. In most cases these tokens are given read-write access to all repositories. A malicious actor with access to this token can execute functionality on behalf of the user with the given permissions of the token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To regenerate a personal access token:
- Sign in to your GitLab account and access the [User settings](../../../../../user/profile/_index.md#access-your-user-settings) left-hand side menu, select "Access tokens"
- Find the access token that was identified in the "Active personal access tokens" table
- Note the permissions that were assigned to this token
- Select the trash icon in the "Action" column of the token
- When prompted, select "Revoke"
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.56 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GitLab personal access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GitLab personal access token was identified. Personal access tokens can be used to access GitLab services as the user who created them. In most cases these tokens are given read-write access to all repositories. A malicious actor with access to this token can execute functionality on behalf of the user with the given permissions of the token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To regenerate a personal access token:
- Sign in to your GitLab account and access the [User settings](../../../../../user/profile/_index.md#access-your-user-settings) left-hand side menu, select "Access tokens"
- Find the access token that was identified in the "Active personal access tokens" table
- Note the permissions that were assigned to this token
- Select the trash icon in the "Action" column of the token
- When prompted, select "Revoke"
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.56 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.50
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.50.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.50.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GoCardless API token
| null |
## Description
The response body contains content that matches the pattern of a GoCardless API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:-------|:-----------|:----|:-----|:-----|
| 798.50 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GoCardless API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GoCardless API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:-------|:-----------|:----|:-----|:-----|
| 798.50 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.124
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.124.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.124.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Typeform personal access token
| null |
## Description
The response body contains content that matches the pattern of a Typeform personal access token was identified. Personal access tokens are for accessing the Typeform API. depending on the assigned scope and permissions, a malicious actor with access to this token can read, update, or delete form data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). To regenerate the Typeform API token: - Sign in to your Typeform account and go to <https://admin.typeform.com/> - In the top right corner, select your profile picture and select "Your settings" under "Account" - In the left-hand menu, select "Personal tokens" - In the "token name" table, find the identified token, select the ellipsis, and select "Regenerate token" For more information, please see [Typeform's documentation on personal access tokens](https://www.typeform.com/developers/get-started/personal-access-token/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.124 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Typeform personal access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Typeform personal access token was identified. Personal access tokens are for accessing the Typeform API. depending on the assigned scope and permissions, a malicious actor with access to this token can read, update, or delete form data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). To regenerate the Typeform API token: - Sign in to your Typeform account and go to <https://admin.typeform.com/> - In the top right corner, select your profile picture and select "Your settings" under "Account" - In the left-hand menu, select "Personal tokens" - In the "token name" table, find the identified token, select the ellipsis, and select "Regenerate token" For more information, please see [Typeform's documentation on personal access tokens](https://www.typeform.com/developers/get-started/personal-access-token/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.124 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.158
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.158.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.158.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Artifactory API Key
| null |
## Description
The response body contains content that matches the pattern of an Artifactory API Key was identified. An Artifactory API Key enable actions like deploying artifacts, managing repositories, configuring permissions, and retrieving artifacts from JFrog Artifactory repositories. If leaked, a malicious actor could use it to exfiltrate sensitive proprietary code, inject malicious packages into the build pipeline, or delete critical artifacts that could disrupt an organization's software delivery capabilities.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.158 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Artifactory API Key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an Artifactory API Key was identified. An Artifactory API Key enable actions like deploying artifacts, managing repositories, configuring permissions, and retrieving artifacts from JFrog Artifactory repositories. If leaked, a malicious actor could use it to exfiltrate sensitive proprietary code, inject malicious packages into the build pipeline, or delete critical artifacts that could disrupt an organization's software delivery capabilities.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.158 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.46
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.46.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.46.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Flutterwave test secret key
| null |
## Description
The response body contains content that matches the pattern of a test Flutterwave secret key was identified. Secret keys have the highest level of privileges and can authorize any action on your account. However, this is a test key so it can only be used for fake transactions. A malicious actor with access to this key can send webhook and email events.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your key:
- Sign in and go to <https://app.flutterwave.com/dashboard/home>
- Select "Settings" on the left-hand menu
- Select "API Keys" under "Developers" on the left-hand menu
- Ensure "Test mode" is activated
- Select "Generate secret key" to rotate the public, secret, and encryption key
For more information, please see the [Flutterwave documentation on authentication](https://developer.flutterwave.com/docs/authentication).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.46 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Flutterwave test secret key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a test Flutterwave secret key was identified. Secret keys have the highest level of privileges and can authorize any action on your account. However, this is a test key so it can only be used for fake transactions. A malicious actor with access to this key can send webhook and email events.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your key:
- Sign in and go to <https://app.flutterwave.com/dashboard/home>
- Select "Settings" on the left-hand menu
- Select "API Keys" under "Developers" on the left-hand menu
- Ensure "Test mode" is activated
- Select "Generate secret key" to rotate the public, secret, and encryption key
For more information, please see the [Flutterwave documentation on authentication](https://developer.flutterwave.com/docs/authentication).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.46 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/601.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/601.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
601.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
URL redirection to untrusted site (open redirect)
| null |
## Description
This site was found to allow open redirects from user supplied input. Open redirects are commonly
abused in phishing attacks where the original domain or URL looks like a legitimate link, but then
redirects a user to a malicious site. An example would be
`https://example.com/redirect?url=https://%62%61%64%2e%63%6f%6d%2f%66%61%6b%65%6c%6f%67%69%6e` which,
when decoded turns into `bad.com/fakelogin`.
## Remediation
Never redirect a client based on user input found in a `GET` request. It is recommended that the list
of target links to redirect a user to are contained server side, and retrieved using a numerical value
as an index to return the link to be redirected to. For example, `/redirect?id=1` would cause the
application to look up the `1` index and return a URL such as `https://example.com`. This URL would
then be used to redirect the user, using the 301 response code and `Location` header.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 601.1 | true | 601 | Passive | Low |
## Links
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)
- [CWE](https://cwe.mitre.org/data/definitions/601.html)
|
---
stage: Application Security Testing
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
title: URL redirection to untrusted site (open redirect)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
This site was found to allow open redirects from user supplied input. Open redirects are commonly
abused in phishing attacks where the original domain or URL looks like a legitimate link, but then
redirects a user to a malicious site. An example would be
`https://example.com/redirect?url=https://%62%61%64%2e%63%6f%6d%2f%66%61%6b%65%6c%6f%67%69%6e` which,
when decoded turns into `bad.com/fakelogin`.
## Remediation
Never redirect a client based on user input found in a `GET` request. It is recommended that the list
of target links to redirect a user to are contained server side, and retrieved using a numerical value
as an index to return the link to be redirected to. For example, `/redirect?id=1` would cause the
application to look up the `1` index and return a URL such as `https://example.com`. This URL would
then be used to redirect the user, using the 301 response code and `Location` header.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 601.1 | true | 601 | Passive | Low |
## Links
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)
- [CWE](https://cwe.mitre.org/data/definitions/601.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.40
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.40.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.40.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Fastly API user or automation token
| null |
## Description
The response body contains content that matches the pattern of a Fastly API user or automation token was identified. Fastly API tokens can grant read write or read only access depending on how they are configured.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke an API token:
- Sign in to the Fastly web interface at <https://manage.fastly.com/account>
- Go to "Account" and then "API Tokens" in the left hand menu
- Find the token you want to delete and note any details about its scope.
- When ready, select the trash icon
- When prompted select "Delete"
For more information, please see [Fastly's documentation on Using API Tokens](https://docs.fastly.com/en/guides/using-api-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.40 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Fastly API user or automation token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Fastly API user or automation token was identified. Fastly API tokens can grant read write or read only access depending on how they are configured.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke an API token:
- Sign in to the Fastly web interface at <https://manage.fastly.com/account>
- Go to "Account" and then "API Tokens" in the left hand menu
- Find the token you want to delete and note any details about its scope.
- When ready, select the trash icon
- When prompted select "Delete"
For more information, please see [Fastly's documentation on Using API Tokens](https://docs.fastly.com/en/guides/using-api-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.40 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/16.10
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.10.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
16.10.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Content-Security-Policy violations
| null |
## Description
A `Content-Security-Policy` (CSP) was identified on the target site that is reporting violations when
attempting to load the page in a browser. This may cause disruption to your users when attempting to visit the page.
## Remediation
Review the violations to determine if any action is necessary.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.10 | true | 16 | Passive | Info |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)
- [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
- [Content Security Policy Level 3](https://www.w3.org/TR/CSP3/)
- [CSP Evaluator](https://csp-evaluator.withgoogle.com/)
|
---
stage: Application Security Testing
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
title: Content-Security-Policy violations
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
A `Content-Security-Policy` (CSP) was identified on the target site that is reporting violations when
attempting to load the page in a browser. This may cause disruption to your users when attempting to visit the page.
## Remediation
Review the violations to determine if any action is necessary.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.10 | true | 16 | Passive | Info |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)
- [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
- [Content Security Policy Level 3](https://www.w3.org/TR/CSP3/)
- [CSP Evaluator](https://csp-evaluator.withgoogle.com/)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.132
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.132.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.132.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token CircleCI Personal Access Token
| null |
## Description
The response body contains content that matches the pattern of a CircleCI personal access token was identified. Personal access tokens grant the same level of permissions as the user that created the token. A malicious actor with access to this token can impersonate the user and gain access to all features and services in CircleCI.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
For rotating a Personal Access token:
- In the CircleCI application, go to your User settings.
- Select "Personal API Tokens".
- Select "X" in the Remove column for the token you wish to replace and confirm your deletion. - Select "Create New Token".
- In the Token name field, type a new name for the old token you are rotating. It can be the same name given to the old token.
- Select "Add API Token".
- After the token appears, copy and paste it to another location. It is not possible to view the token again.
For more information please see their [documentation on rotating personal access tokens](https://circleci.com/docs/managing-api-tokens/#rotating-a-personal-api-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.132 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token CircleCI Personal Access Token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a CircleCI personal access token was identified. Personal access tokens grant the same level of permissions as the user that created the token. A malicious actor with access to this token can impersonate the user and gain access to all features and services in CircleCI.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
For rotating a Personal Access token:
- In the CircleCI application, go to your User settings.
- Select "Personal API Tokens".
- Select "X" in the Remove column for the token you wish to replace and confirm your deletion. - Select "Create New Token".
- In the Token name field, type a new name for the old token you are rotating. It can be the same name given to the old token.
- Select "Add API Token".
- After the token appears, copy and paste it to another location. It is not possible to view the token again.
For more information please see their [documentation on rotating personal access tokens](https://circleci.com/docs/managing-api-tokens/#rotating-a-personal-api-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.132 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.134
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.134.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.134.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Contentful personal access token
| null |
## Description
The response body contains content that matches the pattern of a Contentful personal access token was identified. Personal access tokens are tied to the user who requests them and carry the same permissions, including access to organizations, spaces, and content.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a personal access token:
- Sign in and visit your account profile: <https://app.contentful.com/account/profile/user>
- Select the "CMA tokens" tab in the top menu
- Identify the token that was detected
- Select "Revoke" in the right hand column
- Select "Revoke" when prompted
For more information, please see the developer [documentation on personal access tokens](https://www.contentful.com/help/token-management/personal-access-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.134 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Contentful personal access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Contentful personal access token was identified. Personal access tokens are tied to the user who requests them and carry the same permissions, including access to organizations, spaces, and content.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a personal access token:
- Sign in and visit your account profile: <https://app.contentful.com/account/profile/user>
- Select the "CMA tokens" tab in the top menu
- Identify the token that was detected
- Select "Revoke" in the right hand column
- Select "Revoke" when prompted
For more information, please see the developer [documentation on personal access tokens](https://www.contentful.com/help/token-management/personal-access-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.134 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.148
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.148.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.148.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GitLab Kubernetes agent token
| null |
## Description
The response body contains content that matches the pattern of a GitLab Agent for Kubernetes token was identified. The Kubernetes access token is used to authenticate the GitLab agent for Kubernetes with a Kubernetes cluster. A malicious actor with access to this token can access source code in the agent's configuration project, access source code in any public project on the GitLab instance, or even, under very specific conditions, obtain a Kubernetes manifest.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). For more information please see [GitLabs documentation on rotating the Kubernetes agent token](../../../../../user/clusters/agent/work_with_agent.md#reset-the-agent-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.148 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GitLab Kubernetes agent token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GitLab Agent for Kubernetes token was identified. The Kubernetes access token is used to authenticate the GitLab agent for Kubernetes with a Kubernetes cluster. A malicious actor with access to this token can access source code in the agent's configuration project, access source code in any public project on the GitLab instance, or even, under very specific conditions, obtain a Kubernetes manifest.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). For more information please see [GitLabs documentation on rotating the Kubernetes agent token](../../../../../user/clusters/agent/work_with_agent.md#reset-the-agent-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.148 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.102
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.102.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.102.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Brevo API token
| null |
## Description
The response body contains content that matches the pattern of a Brevo API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.102 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Brevo API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Brevo API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.102 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.104
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.104.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.104.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Shippo API token
| null |
## Description
The response body contains content that matches the pattern of a live Shippo API token was identified. API tokens can be used to access the Shippo API which is used for shipping services. A malicious actor with access to this token can access billing and order information and modify shipping data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke an API token:
- Sign in to your Shippo account and access <https://apps.goshippo.com/>
- In the top right-hand side, select the "gear" icon to go to the "Settings" page
- Scroll down in the left hand menu to "Advanced" and select "API"
- Under the "Token" section, select "Manage your token"
- Find the identified token and select the trash icon
- When prompted, select "Yes, remove token" in the "Manage Your Tokens" dialog
For more information, please see [Shippo's documentation on API keys](https://portal.goshippo.com/api-config/api).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.104 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Shippo API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a live Shippo API token was identified. API tokens can be used to access the Shippo API which is used for shipping services. A malicious actor with access to this token can access billing and order information and modify shipping data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke an API token:
- Sign in to your Shippo account and access <https://apps.goshippo.com/>
- In the top right-hand side, select the "gear" icon to go to the "Settings" page
- Scroll down in the left hand menu to "Advanced" and select "API"
- Under the "Token" section, select "Manage your token"
- Find the identified token and select the trash icon
- When prompted, select "Yes, remove token" in the "Manage Your Tokens" dialog
For more information, please see [Shippo's documentation on API keys](https://portal.goshippo.com/api-config/api).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.104 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.178
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.178.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.178.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Stripe restricted test key
| null |
## Description
The response body contains content that matches the pattern of a Stripe restricted test key was identified. Test restricted keys offer greater security by only allowing read or write access to specific API resources. A malicious actor with access to this key is limited by the scope defined and can only access test data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your Stripe restricted test key:
- Sign in to your Stripe account and access <https://dashboard.stripe.com/apikeys>
- Ensure "Test mode" is enabled by selecting the toggle in the top menu
- In the "Restricted keys" section, find the key that was identified and select the ellipsis in the right-hand side
- Select "Roll key..."
- In the "Roll API key" dialog, select an expiration date, for example "now"
- Select "Roll API Key"
For more information, please see [Stripe's documentation on rotating API keys](https://docs.stripe.com/keys#rolling-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.178 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Stripe restricted test key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Stripe restricted test key was identified. Test restricted keys offer greater security by only allowing read or write access to specific API resources. A malicious actor with access to this key is limited by the scope defined and can only access test data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your Stripe restricted test key:
- Sign in to your Stripe account and access <https://dashboard.stripe.com/apikeys>
- Ensure "Test mode" is enabled by selecting the toggle in the top menu
- In the "Restricted keys" section, find the key that was identified and select the ellipsis in the right-hand side
- Select "Roll key..."
- In the "Roll API key" dialog, select an expiration date, for example "now"
- Select "Roll API Key"
For more information, please see [Stripe's documentation on rotating API keys](https://docs.stripe.com/keys#rolling-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.178 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/548.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/548.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
548.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of information through directory listing
| null |
## Description
The target web server is configured to list the contents of directories that do not contain an index file
such as `index.html`. This could lead to accidental exposure of sensitive information, or give an attacker
details on how filenames and directories are structured and stored.
## Remediation
Directory indexing should be disabled.
Apache:
For Apache-based web sites, ensure all `<Directory>` definitions have `Options -Indexes` configured in the
`apache2.conf` or `httpd.conf` configuration file.
NGINX:
For NGINX-based websites, ensure all `location` definitions have the `autoindex off` directive set in the
`nginx.conf` file.
IIS:
For IIS-based websites version 7.0 and later, you can use the `<directoryBrowse enabled="false" />` element
in the `applicationHost.config` or `Web.config` files.
For all other server types, consult your product's documentation on how to disable directory
indexing.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 548.1 | false | 548 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/548.html)
- [Apache Options](https://httpd.apache.org/docs/2.4/mod/core.html#options)
- [NGINX `autoindex`](https://nginx.org/en/docs/http/ngx_http_autoindex_module.html)
- [IIS `directoryBrowse` element](https://learn.microsoft.com/en-us/iis/configuration/system.webserver/directorybrowse)
|
---
stage: Application Security Testing
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
title: Exposure of information through directory listing
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The target web server is configured to list the contents of directories that do not contain an index file
such as `index.html`. This could lead to accidental exposure of sensitive information, or give an attacker
details on how filenames and directories are structured and stored.
## Remediation
Directory indexing should be disabled.
Apache:
For Apache-based web sites, ensure all `<Directory>` definitions have `Options -Indexes` configured in the
`apache2.conf` or `httpd.conf` configuration file.
NGINX:
For NGINX-based websites, ensure all `location` definitions have the `autoindex off` directive set in the
`nginx.conf` file.
IIS:
For IIS-based websites version 7.0 and later, you can use the `<directoryBrowse enabled="false" />` element
in the `applicationHost.config` or `Web.config` files.
For all other server types, consult your product's documentation on how to disable directory
indexing.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 548.1 | false | 548 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/548.html)
- [Apache Options](https://httpd.apache.org/docs/2.4/mod/core.html#options)
- [NGINX `autoindex`](https://nginx.org/en/docs/http/ngx_http_autoindex_module.html)
- [IIS `directoryBrowse` element](https://learn.microsoft.com/en-us/iis/configuration/system.webserver/directorybrowse)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.91
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.91.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.91.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token PlanetScale API token
| null |
## Description
The response body contains content that matches the pattern of a PlanetScale API service token was identified. Service tokens are created and assigned permissions depending on the allowed scope. A malicious actor with access to the service token is granted the same permissions that were assigned to this service token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a service token:
- Sign in to your PlanetScale account and access <https://app.planetscale.com/>.
- From the menu on the left-hand side, select "Settings"
- Under "Settings", select "Service tokens"
- Find the identified security token and select its name
- Take note of its organization access, permissions and scope
- Select "Delete service token" in the top right corner
- When prompted, select "Delete" in the "Delete service token" dialog
For more information, please see [PlanetScale's documentation on service tokens](https://planetscale.com/docs/concepts/service-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.91 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token PlanetScale API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a PlanetScale API service token was identified. Service tokens are created and assigned permissions depending on the allowed scope. A malicious actor with access to the service token is granted the same permissions that were assigned to this service token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a service token:
- Sign in to your PlanetScale account and access <https://app.planetscale.com/>.
- From the menu on the left-hand side, select "Settings"
- Under "Settings", select "Service tokens"
- Find the identified security token and select its name
- Take note of its organization access, permissions and scope
- Select "Delete service token" in the top right corner
- When prompted, select "Delete" in the "Delete service token" dialog
For more information, please see [PlanetScale's documentation on service tokens](https://planetscale.com/docs/concepts/service-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.91 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/598.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/598.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
598.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Use of GET request method with sensitive query strings (session ID)
| null |
## Description
A session ID was identified in the request URL as well as a cookie value. Session
IDs should not be sent in GET requests as they maybe captured by proxy systems, stored in
browser history, or stored in log files. If an attacker were to get access to the session
ID they would potentially be able to gain access to the target account.
## Remediation
As request headers are rarely logged or captured by third party systems, ensure session ID
values are only sent in cookies (assigned via `Set-Cookie` response headers) and never sent
in the request URL.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 598.1 | true | 598 | Passive | Medium |
## Links
- [OWASP](https://owasp.org/www-community/vulnerabilities/Information_exposure_through_query_strings_in_url)
- [CWE](https://cwe.mitre.org/data/definitions/598.html)
|
---
stage: Application Security Testing
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
title: Use of GET request method with sensitive query strings (session ID)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
A session ID was identified in the request URL as well as a cookie value. Session
IDs should not be sent in GET requests as they maybe captured by proxy systems, stored in
browser history, or stored in log files. If an attacker were to get access to the session
ID they would potentially be able to gain access to the target account.
## Remediation
As request headers are rarely logged or captured by third party systems, ensure session ID
values are only sent in cookies (assigned via `Set-Cookie` response headers) and never sent
in the request URL.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 598.1 | true | 598 | Passive | Medium |
## Links
- [OWASP](https://owasp.org/www-community/vulnerabilities/Information_exposure_through_query_strings_in_url)
- [CWE](https://cwe.mitre.org/data/definitions/598.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.70
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.70.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.70.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Lob API key
| null |
## Description
The response body contains content that matches the pattern of a Lob API key was identified. API keys can be used to verify addresses, create campaigns, print, or mail directly to customers. A malicious actor with access to this key can perform any API request to Lob without restriction.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate an API key:
- Sign in to your account and go to <https://dashboard.lob.com/>
- In the bottom left corner select the gear icon / "Settings" menu option
- Under "Settings" select the "API Keys" tab
- Under the "Live Environment" in the "Secret API Keys" section, select the rotate arrow icon
- When prompted, select "Yes" in the "Rotate Secret Live API Key" dialog
For more information, please see [Lob's documentation on API keys](https://docs.lob.com/#tag/Authentication/API-Keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.70 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Lob API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Lob API key was identified. API keys can be used to verify addresses, create campaigns, print, or mail directly to customers. A malicious actor with access to this key can perform any API request to Lob without restriction.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate an API key:
- Sign in to your account and go to <https://dashboard.lob.com/>
- In the bottom left corner select the gear icon / "Settings" menu option
- Under "Settings" select the "API Keys" tab
- Under the "Live Environment" in the "Secret API Keys" section, select the rotate arrow icon
- When prompted, select "Yes" in the "Rotate Secret Live API Key" dialog
For more information, please see [Lob's documentation on API keys](https://docs.lob.com/#tag/Authentication/API-Keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.70 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.97
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.97.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.97.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token RubyGems API token
| null |
## Description
The response body contains content that matches the pattern of a RubyGems API token was identified. RubyGems tokens are used for accessing the API or publishing packages. RubyGems tokens can be created with specific permissions or scopes. Depending on the permissions and scope, a malicious actor with access to this token can add or remove packages, add or remove owners, or view the dashboard.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the API token:
- Sign in to your RubyGems account and access <https://rubygems.org/settings/edit>
- Scroll down to and select "API Keys" or go to <https://rubygems.org/profile/api_keys>
- Find the identified token and select "Delete"
- When prompted, select "OK" in the dialog.
For more information, please see the [RubyGems documentation on API tokens](https://guides.rubygems.org/api-key-scopes/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:-------|:-----------|:----|:-----|:-----|
| 798.97 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token RubyGems API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a RubyGems API token was identified. RubyGems tokens are used for accessing the API or publishing packages. RubyGems tokens can be created with specific permissions or scopes. Depending on the permissions and scope, a malicious actor with access to this token can add or remove packages, add or remove owners, or view the dashboard.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the API token:
- Sign in to your RubyGems account and access <https://rubygems.org/settings/edit>
- Scroll down to and select "API Keys" or go to <https://rubygems.org/profile/api_keys>
- Find the identified token and select "Delete"
- When prompted, select "OK" in the dialog.
For more information, please see the [RubyGems documentation on API tokens](https://guides.rubygems.org/api-key-scopes/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:-------|:-----------|:----|:-----|:-----|
| 798.97 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/359.2
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/359.2.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
359.2.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of Private Personal Information (PII) to an unauthorized actor (United States social security number)
| null |
## Description
The target application was found to return Social Security Number (SSN) information in the response. Organizations
found returning such information may be in violation of (United States) state or federal laws and may face stiff penalties.
## Remediation
PII such as social security numbers should never be directly returned to the user. The majority of the information
should masked except the last few digits or characters of the identifier. For example, social security numbers
only be displayed with the last four digits: `***-**-1234`. Ensure this masking is done on the server
and only then send the masked data back to the client. Do not rely on client side JavaScript or other methods
to mask these values as the data could still be intercepted or unmasked.
Additionally, social security numbers should never be stored un-encrypted in files or databases.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 359.2 | true | 359 | Passive | Medium |
## Links
- [OWASP Top 10 A3 2017 - Sensitive Data Exposure](https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure)
- [CWE](https://cwe.mitre.org/data/definitions/359.html)
- [Privacy Act (CMPPA)](https://www.ssa.gov/dataexchange/privacyinfo.html)
|
---
stage: Application Security Testing
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
title: Exposure of Private Personal Information (PII) to an unauthorized actor (United
States social security number)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The target application was found to return Social Security Number (SSN) information in the response. Organizations
found returning such information may be in violation of (United States) state or federal laws and may face stiff penalties.
## Remediation
PII such as social security numbers should never be directly returned to the user. The majority of the information
should masked except the last few digits or characters of the identifier. For example, social security numbers
only be displayed with the last four digits: `***-**-1234`. Ensure this masking is done on the server
and only then send the masked data back to the client. Do not rely on client side JavaScript or other methods
to mask these values as the data could still be intercepted or unmasked.
Additionally, social security numbers should never be stored un-encrypted in files or databases.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 359.2 | true | 359 | Passive | Medium |
## Links
- [OWASP Top 10 A3 2017 - Sensitive Data Exposure](https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure)
- [CWE](https://cwe.mitre.org/data/definitions/359.html)
- [Privacy Act (CMPPA)](https://www.ssa.gov/dataexchange/privacyinfo.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.168
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.168.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.168.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token RSA private key
| null |
## Description
The response body contains content that matches the pattern of an RSA private key was identified. Private RSA keys can be used in many types of applications but generally are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To generate a new RSA key, use the `ssh-keygen` tool:
```console ssh-keygen -m PEM -t rsa -b 4096 -C "email@company.com"```
For more information, please see the [`ssh-keygen` documentation](https://linux.die.net/man/1/ssh-keygen).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.168 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token RSA private key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an RSA private key was identified. Private RSA keys can be used in many types of applications but generally are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To generate a new RSA key, use the `ssh-keygen` tool:
```console ssh-keygen -m PEM -t rsa -b 4096 -C "email@company.com"```
For more information, please see the [`ssh-keygen` documentation](https://linux.die.net/man/1/ssh-keygen).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.168 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.66
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.66.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.66.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Linear API token
| null |
## Description
The response body contains content that matches the pattern of a Linear API token was identified. Personal API tokens can be used to access Linear's GraphQL API. A malicious actor with access to this token can read or write issues, projects and teams to Linear and any systems the account has been integrated with.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Linear API token:
- Sign in to your account at <https://linear.app/>
- Select your organization in the top left corner and select "Preferences"
- In the left-hand menu, select "API" under "My Account"
- Find the identified API key in the "Personal API Keys" section of the page
- Select "Revoke" next to the identified key
- When prompted, select "Revoke" in the "Revoke access?" dialog
For more information, please see [Linear's documentation on using personal API keys](https://developers.linear.app/docs/graphql/working-with-the-graphql-api#personal-api-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.66 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Linear API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Linear API token was identified. Personal API tokens can be used to access Linear's GraphQL API. A malicious actor with access to this token can read or write issues, projects and teams to Linear and any systems the account has been integrated with.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Linear API token:
- Sign in to your account at <https://linear.app/>
- Select your organization in the top left corner and select "Preferences"
- In the left-hand menu, select "API" under "My Account"
- Find the identified API key in the "Personal API Keys" section of the page
- Select "Revoke" next to the identified key
- When prompted, select "Revoke" in the "Revoke access?" dialog
For more information, please see [Linear's documentation on using personal API keys](https://developers.linear.app/docs/graphql/working-with-the-graphql-api#personal-api-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.66 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.81
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.81.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.81.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token New Relic user API key
| null |
## Description
The response body contains content that matches the pattern of a New Relic user API key was identified. User keys are used for querying data and managing configurations (Alerts, Synthetics, dashboards, etc.). A malicious actor with access to this key can execute API requests as the user who created it.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). For more information, please see [New Relic's documentation on rotating API keys](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#rotate-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.81 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token New Relic user API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a New Relic user API key was identified. User keys are used for querying data and managing configurations (Alerts, Synthetics, dashboards, etc.). A malicious actor with access to this key can execute API requests as the user who created it.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). For more information, please see [New Relic's documentation on rotating API keys](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#rotate-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.81 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.60
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.60.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.60.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token HubSpot private app API token
| null |
## Description
The response body contains content that matches the pattern of a HubSpot private app API token was identified. Private apps allow you to use HubSpot's APIs to access specific data from your HubSpot account and can be restricted by setting specific scopes. A malicious actor with access to this token can call API endpoints with the same levels as those set in the scope of the application. This could be anywhere from only reading marketing campaigns to accessing user and account information and sending emails.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate a private app API token:
- Sign in to your HubSpot account at <https://app.hubspot.com/>
- In the left-hand menu, hover over the database icon and select "Integrations"
- Find the private app that has the identified token and select its name
- Select the "Auth" tab in the top of the page
- In the "Access token" section of the page, select "Rotate"
- Select "Rotate and expire this token now" when prompted
- Select "Rotate now" in the "Rotate access token now?" dialog
For more information, please see [HubSpot's documentation on private apps](https://developers.hubspot.com/beta-docs/guides/apps/private-apps/overview)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.60 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token HubSpot private app API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a HubSpot private app API token was identified. Private apps allow you to use HubSpot's APIs to access specific data from your HubSpot account and can be restricted by setting specific scopes. A malicious actor with access to this token can call API endpoints with the same levels as those set in the scope of the application. This could be anywhere from only reading marketing campaigns to accessing user and account information and sending emails.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate a private app API token:
- Sign in to your HubSpot account at <https://app.hubspot.com/>
- In the left-hand menu, hover over the database icon and select "Integrations"
- Find the private app that has the identified token and select its name
- Select the "Auth" tab in the top of the page
- In the "Access token" section of the page, select "Rotate"
- Select "Rotate and expire this token now" when prompted
- Select "Rotate now" in the "Rotate access token now?" dialog
For more information, please see [HubSpot's documentation on private apps](https://developers.hubspot.com/beta-docs/guides/apps/private-apps/overview)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.60 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/16.7
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.7.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
16.7.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Strict-Transport-Security header missing or invalid
| null |
## Description
The `Strict-Transport-Security` header was found to be missing or invalid. The `Strict-Transport-Security`
header allows web site operators to force communications to occur over a TLS connection. By enabling this
header, websites can protect their users from various forms of network eavesdropping or interception attacks.
While most browsers prevent mixed-content (loading resources from HTTP when navigating from an HTTPS site),
this header also ensures that all resource requests are only ever initiated over a secure transport.
## Remediation
Only three directives are applicable for the `Strict-Transport-Security` header.
1. `max-age`: This required directive specifies how long (in seconds) after receiving the response it should communicate only over a secure transport.
1. `includeSubDomains`: This optional, valueless directive signals that the policy applies to this host as well as any subdomains found under this host's domain.
1. `preload`: While not part of the specification, setting this optional value allows major browser organizations to add this site into the browser's preloaded set of HTTPS sites. This requires further action on behalf of the website operator to submit their domain to the browser's HSTS preload list. See [hstspreload.org](https://hstspreload.org/) for more information.
Invalid directives, or the `Strict-Transport-Security` header appearing more than once (if the values are
different), are considered invalid.
Prior to adding to this security configuration to your website, it is recommended you review the hstspreload.org [Deployment Recommendations](https://hstspreload.org/#deployment-recommendations).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.7 | true | 16 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [Deployment Recommendations](https://hstspreload.org/#deployment-recommendations)
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html)
- [RFC](https://datatracker.ietf.org/doc/html/rfc6797)
|
---
stage: Application Security Testing
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
title: Strict-Transport-Security header missing or invalid
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The `Strict-Transport-Security` header was found to be missing or invalid. The `Strict-Transport-Security`
header allows web site operators to force communications to occur over a TLS connection. By enabling this
header, websites can protect their users from various forms of network eavesdropping or interception attacks.
While most browsers prevent mixed-content (loading resources from HTTP when navigating from an HTTPS site),
this header also ensures that all resource requests are only ever initiated over a secure transport.
## Remediation
Only three directives are applicable for the `Strict-Transport-Security` header.
1. `max-age`: This required directive specifies how long (in seconds) after receiving the response it should communicate only over a secure transport.
1. `includeSubDomains`: This optional, valueless directive signals that the policy applies to this host as well as any subdomains found under this host's domain.
1. `preload`: While not part of the specification, setting this optional value allows major browser organizations to add this site into the browser's preloaded set of HTTPS sites. This requires further action on behalf of the website operator to submit their domain to the browser's HSTS preload list. See [hstspreload.org](https://hstspreload.org/) for more information.
Invalid directives, or the `Strict-Transport-Security` header appearing more than once (if the values are
different), are considered invalid.
Prior to adding to this security configuration to your website, it is recommended you review the hstspreload.org [Deployment Recommendations](https://hstspreload.org/#deployment-recommendations).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.7 | true | 16 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [Deployment Recommendations](https://hstspreload.org/#deployment-recommendations)
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html)
- [RFC](https://datatracker.ietf.org/doc/html/rfc6797)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.118
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.118.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.118.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Twitch OAuth client secret
| null |
## Description
The response body contains content that matches the pattern of a Twitch OAuth client secret was identified. OAuth client secrets are used to allow the service to execute functionality on behalf of Twitch users. A malicious actor with access to this client secret can impersonate the service and execute functionality on behalf its users.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate the OAuth client secret:
- Sign in to your Twitch account and access <https://dev.twitch.tv/console>
- Find the extension that uses the identified key
- Select "Manage" next to extension name in the "Extensions" section
- In the top right corner, select "Extension Settings"
- In the "Twitch API Client Configuration" section, select "Generate Secret" under "Twitch API Client Secret"
- When prompted, select "OK" from the dialog
For more information, please see [Twitch's developer documentation on OAuth](https://dev.twitch.tv/docs/authentication/getting-tokens-oauth/#authorization-code-grant-flow).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.118 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Twitch OAuth client secret
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Twitch OAuth client secret was identified. OAuth client secrets are used to allow the service to execute functionality on behalf of Twitch users. A malicious actor with access to this client secret can impersonate the service and execute functionality on behalf its users.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate the OAuth client secret:
- Sign in to your Twitch account and access <https://dev.twitch.tv/console>
- Find the extension that uses the identified key
- Select "Manage" next to extension name in the "Extensions" section
- In the top right corner, select "Extension Settings"
- In the "Twitch API Client Configuration" section, select "Generate Secret" under "Twitch API Client Secret"
- When prompted, select "OK" from the dialog
For more information, please see [Twitch's developer documentation on OAuth](https://dev.twitch.tv/docs/authentication/getting-tokens-oauth/#authorization-code-grant-flow).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.118 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.164
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.164.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.164.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token OpenAI API key
| null |
## Description
The response body contains content that matches the pattern of a OpenAI API key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.164 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token OpenAI API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a OpenAI API key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.164 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.183
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.183.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.183.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Yandex Cloud IAM cookie v1-3
| null |
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM API key v1.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.183 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Yandex Cloud IAM cookie v1-3
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM API key v1.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.183 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/16.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
16.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Missing Content-Type header
| null |
## Description
The `Content-Type` header ensures that user agents correctly interpret the data being received. Without this header
being sent, the browser may misinterpret the data, leading to MIME confusion attacks. If an attacker were able
to upload files that are accessible by using a browser, they could upload files that may be interpreted as
HTML and so execute Cross-Site Scripting (XSS) attacks.
## Remediation
Ensure all resources return a proper `Content-Type` header that matches their format. As an example,
when returning JavaScript files, the response header should be: `Content-Type: application/javascript`
For added protection, we recommend that all resources return the `X-Content-Type-Options: nosniff`
header to disable user agents from mis-interpreting resources.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.1 | true | 16 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [Mozilla Blog on MIME Confusion attacks](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
|
---
stage: Application Security Testing
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
title: Missing Content-Type header
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The `Content-Type` header ensures that user agents correctly interpret the data being received. Without this header
being sent, the browser may misinterpret the data, leading to MIME confusion attacks. If an attacker were able
to upload files that are accessible by using a browser, they could upload files that may be interpreted as
HTML and so execute Cross-Site Scripting (XSS) attacks.
## Remediation
Ensure all resources return a proper `Content-Type` header that matches their format. As an example,
when returning JavaScript files, the response header should be: `Content-Type: application/javascript`
For added protection, we recommend that all resources return the `X-Content-Type-Options: nosniff`
header to disable user agents from mis-interpreting resources.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.1 | true | 16 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [Mozilla Blog on MIME Confusion attacks](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.162
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.162.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.162.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Oculus access token
| null |
## Description
The response body contains content that matches the pattern of an Oculus access token was identified. User tokens are needed any time your app calls an API to read, modify or write a specific person's Oculus data on their behalf. A malicious actor with access to this token can call the Oculus API on behalf of a specific user of the service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate an Oculus access token:
- Sign in to your Oculus developer account at <https://developer.oculus.com/>
- Select "Development" in the left-hand side menu, and then select "API"
- Under "User Token" select "Generate Token"
For more information, please see [Meta's documentation on protecting access tokens](https://developers.meta.com/horizon/resources/publish-sec-details#protecting-credentials-and-access-tokens)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.162 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Oculus access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an Oculus access token was identified. User tokens are needed any time your app calls an API to read, modify or write a specific person's Oculus data on their behalf. A malicious actor with access to this token can call the Oculus API on behalf of a specific user of the service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate an Oculus access token:
- Sign in to your Oculus developer account at <https://developer.oculus.com/>
- Select "Development" in the left-hand side menu, and then select "API"
- Under "User Token" select "Generate Token"
For more information, please see [Meta's documentation on protecting access tokens](https://developers.meta.com/horizon/resources/publish-sec-details#protecting-credentials-and-access-tokens)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.162 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.10
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.10.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.10.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Asana client secret
| null |
## Description
The response body contains content that matches the pattern of an Asana Client Secret was detected. Client Secrets are used for authentication and authorization using OAuth. A malicious actor who got access to this secret could gain access to user accounts and execute functionality on their behalf.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). To revoke the detected client secret: - Sign in to your developer account and access <https://app.asana.com/0/my-apps> - Under the "My apps" page find the application that uses the secret - Select your app in the developer console - Go to the "OAuth" tab in the sidebar - Select "Reset" next to your client secret For more information please [see their documentation on configuring OAuth](https://developers.asana.com/docs/oauth)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.10 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Asana client secret
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an Asana Client Secret was detected. Client Secrets are used for authentication and authorization using OAuth. A malicious actor who got access to this secret could gain access to user accounts and execute functionality on their behalf.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). To revoke the detected client secret: - Sign in to your developer account and access <https://app.asana.com/0/my-apps> - Under the "My apps" page find the application that uses the secret - Select your app in the developer console - Go to the "OAuth" tab in the sidebar - Select "Reset" next to your client secret For more information please [see their documentation on configuring OAuth](https://developers.asana.com/docs/oauth)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.10 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/918.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/918.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
918.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Server-Side Request Forgery
| null |
## Description
The application is susceptible to Server-Side Request Forgery (SSRF), a high-risk vulnerability
that allows attackers to make unauthorized requests to internal and external resources. This
vulnerability arises when user-controlled input is not properly validated or sanitized before
being used in requests to resources, enabling attackers to manipulate these requests for
malicious purposes.
## Remediation
Avoid using user-supplied data for constructing requests. If there is a business need for this,
consider an allowlist approach and/or block requests to internal resources using firewall
rules or a robust request library with anti-SSRF support.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 918.1 | false | 918 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/918.html)
- [OWASP](https://owasp.org/www-community/attacks/Server_Side_Request_Forgery)
- [Server-Side Request Forgery Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html)
|
---
stage: Application Security Testing
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
title: Server-Side Request Forgery
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The application is susceptible to Server-Side Request Forgery (SSRF), a high-risk vulnerability
that allows attackers to make unauthorized requests to internal and external resources. This
vulnerability arises when user-controlled input is not properly validated or sanitized before
being used in requests to resources, enabling attackers to manipulate these requests for
malicious purposes.
## Remediation
Avoid using user-supplied data for constructing requests. If there is a business need for this,
consider an allowlist approach and/or block requests to internal resources using firewall
rules or a robust request library with anti-SSRF support.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 918.1 | false | 918 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/918.html)
- [OWASP](https://owasp.org/www-community/attacks/Server_Side_Request_Forgery)
- [Server-Side Request Forgery Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/checks
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/_index.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
_index.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
DAST browser-based crawler vulnerability checks
| null |
<!--
This file is autogenerated. Do not edit directly.
See: https://gitlab.com/gitlab-org/security-products/dast-cwe-checks/-/blob/main/doc/how-to-generate-the-markdown-documentation.md
-->
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
The [DAST browser-based crawler](../_index.md) provides vulnerability checks that are used to
scan for vulnerabilities in the site under test.
## Passive Checks
| ID | Check | Severity | Type |
|:----------------------|:---------------------------------------------------------------------------------------------------------------|:---------|:-----|
| [1004.1](1004.1.md) | Sensitive cookie without HttpOnly attribute | Low | Passive |
| [16.1](16.1.md) | Missing Content-Type header | Low | Passive |
| [16.10](16.10.md) | Content-Security-Policy violations | Info | Passive |
| [16.2](16.2.md) | Server header exposes version information | Low | Passive |
| [16.3](16.3.md) | X-Powered-By header exposes version information | Low | Passive |
| [16.4](16.4.md) | X-Backend-Server header exposes server information | Info | Passive |
| [16.5](16.5.md) | AspNet header exposes version information | Low | Passive |
| [16.6](16.6.md) | AspNetMvc header exposes version information | Low | Passive |
| [16.7](16.7.md) | Strict-Transport-Security header missing or invalid | Low | Passive |
| [16.8](16.8.md) | Content-Security-Policy analysis | Info | Passive |
| [16.9](16.9.md) | Content-Security-Policy-Report-Only analysis | Info | Passive |
| [200.1](200.1.md) | Exposure of sensitive information to an unauthorized actor (private IP address) | Low | Passive |
| [209.1](209.1.md) | Generation of error message containing sensitive information | Low | Passive |
| [209.2](209.2.md) | Generation of database error message containing sensitive information | Low | Passive |
| [287.1](287.1.md) | Insecure authentication over HTTP (Basic Authentication) | Medium | Passive |
| [287.2](287.2.md) | Insecure authentication over HTTP (Digest Authentication) | Low | Passive |
| [319.1](319.1.md) | Mixed Content | Info | Passive |
| [352.1](352.1.md) | Absence of anti-CSRF tokens | Medium | Passive |
| [359.1](359.1.md) | Exposure of Private Personal Information (PII) to an unauthorized actor (credit card) | Medium | Passive |
| [359.2](359.2.md) | Exposure of Private Personal Information (PII) to an unauthorized actor (United States social security number) | Medium | Passive |
| [548.1](548.1.md) | Exposure of information through directory listing | Low | Passive |
| [598.1](598.1.md) | Use of GET request method with sensitive query strings (session ID) | Medium | Passive |
| [598.2](598.2.md) | Use of GET request method with sensitive query strings (password) | Medium | Passive |
| [598.3](598.3.md) | Use of GET request method with sensitive query strings (Authorization header details) | Medium | Passive |
| [601.1](601.1.md) | URL redirection to untrusted site ('open redirect') | Low | Passive |
| [614.1](614.1.md) | Sensitive cookie without Secure attribute | Low | Passive |
| [693.1](693.1.md) | Missing X-Content-Type-Options: nosniff | Low | Passive |
| [798.2](798.2.md) | Exposure of confidential secret or token Adobe Client ID (OAuth Web) | High | Passive |
| [798.3](798.3.md) | Exposure of confidential secret or token Adobe client secret | High | Passive |
| [798.4](798.4.md) | Exposure of confidential secret or token Age secret key | High | Passive |
| [798.7](798.7.md) | Exposure of confidential secret or token Alibaba AccessKey ID | High | Passive |
| [798.8](798.8.md) | Exposure of confidential secret or token Alibaba Secret Key | High | Passive |
| [798.9](798.9.md) | Exposure of confidential secret or token Asana client ID | High | Passive |
| [798.10](798.10.md) | Exposure of confidential secret or token Asana client secret | High | Passive |
| [798.11](798.11.md) | Exposure of confidential secret or token Atlassian API token | High | Passive |
| [798.12](798.12.md) | Exposure of confidential secret or token AWS access token | High | Passive |
| [798.13](798.13.md) | Exposure of confidential secret or token Bitbucket client ID | High | Passive |
| [798.14](798.14.md) | Exposure of confidential secret or token Bitbucket client secret | High | Passive |
| [798.17](798.17.md) | Exposure of confidential secret or token Beamer API token | High | Passive |
| [798.20](798.20.md) | Exposure of confidential secret or token Clojars deploy token | High | Passive |
| [798.23](798.23.md) | Exposure of confidential secret or token Contentful delivery API token | High | Passive |
| [798.24](798.24.md) | Exposure of confidential secret or token Databricks API token | High | Passive |
| [798.26](798.26.md) | Exposure of confidential secret or token Discord API key | High | Passive |
| [798.27](798.27.md) | Exposure of confidential secret or token Discord client ID | High | Passive |
| [798.28](798.28.md) | Exposure of confidential secret or token Discord client secret | High | Passive |
| [798.29](798.29.md) | Exposure of confidential secret or token Doppler API token | High | Passive |
| [798.30](798.30.md) | Exposure of confidential secret or token Dropbox API secret/key | High | Passive |
| [798.31](798.31.md) | Exposure of confidential secret or token Dropbox long lived API token | High | Passive |
| [798.32](798.32.md) | Exposure of confidential secret or token Dropbox short lived API token | High | Passive |
| [798.34](798.34.md) | Exposure of confidential secret or token Duffel API token | High | Passive |
| [798.35](798.35.md) | Exposure of confidential secret or token Dynatrace API token | High | Passive |
| [798.36](798.36.md) | Exposure of confidential secret or token EasyPost production API key | High | Passive |
| [798.37](798.37.md) | Exposure of confidential secret or token EasyPost test API key | High | Passive |
| [798.39](798.39.md) | Exposure of confidential secret or token Facebook token | High | Passive |
| [798.40](798.40.md) | Exposure of confidential secret or token Fastly API user or automation token | High | Passive |
| [798.41](798.41.md) | Exposure of confidential secret or token Finicity client secret | High | Passive |
| [798.42](798.42.md) | Exposure of confidential secret or token Finicity API token | High | Passive |
| [798.46](798.46.md) | Exposure of confidential secret or token Flutterwave test secret key | High | Passive |
| [798.47](798.47.md) | Exposure of confidential secret or token Flutterwave test encrypted key | High | Passive |
| [798.48](798.48.md) | Exposure of confidential secret or token Frame.io API token | High | Passive |
| [798.50](798.50.md) | Exposure of confidential secret or token GoCardless API token | High | Passive |
| [798.52](798.52.md) | Exposure of confidential secret or token GitHub personal access token (classic) | High | Passive |
| [798.53](798.53.md) | Exposure of confidential secret or token GitHub OAuth Access Token | High | Passive |
| [798.54](798.54.md) | Exposure of confidential secret or token GitHub app token | High | Passive |
| [798.55](798.55.md) | Exposure of confidential secret or token GitHub refresh token | High | Passive |
| [798.56](798.56.md) | Exposure of confidential secret or token GitLab personal access token | High | Passive |
| [798.58](798.58.md) | Exposure of confidential secret or token HashiCorp Terraform API token | High | Passive |
| [798.59](798.59.md) | Exposure of confidential secret or token Heroku API key or application authorization token | High | Passive |
| [798.60](798.60.md) | Exposure of confidential secret or token HubSpot private app API token | High | Passive |
| [798.61](798.61.md) | Exposure of confidential secret or token Intercom API token | High | Passive |
| [798.66](798.66.md) | Exposure of confidential secret or token Linear API token | High | Passive |
| [798.67](798.67.md) | Exposure of confidential secret or token Linear client secret or ID (OAuth 2.0) | High | Passive |
| [798.68](798.68.md) | Exposure of confidential secret or token LinkedIn client ID | High | Passive |
| [798.69](798.69.md) | Exposure of confidential secret or token LinkedIn client secret | High | Passive |
| [798.70](798.70.md) | Exposure of confidential secret or token Lob API key | High | Passive |
| [798.72](798.72.md) | Exposure of confidential secret or token Mailchimp API key | High | Passive |
| [798.74](798.74.md) | Exposure of confidential secret or token Mailgun private API token | High | Passive |
| [798.75](798.75.md) | Exposure of confidential secret or token Mailgun webhook signing key | High | Passive |
| [798.78](798.78.md) | Exposure of confidential secret or token MessageBird access key | High | Passive |
| [798.81](798.81.md) | Exposure of confidential secret or token New Relic user API key | High | Passive |
| [798.82](798.82.md) | Exposure of confidential secret or token New Relic user API ID | High | Passive |
| [798.83](798.83.md) | Exposure of confidential secret or token New Relic ingest browser API token | High | Passive |
| [798.84](798.84.md) | Exposure of confidential secret or token npm access token | High | Passive |
| [798.90](798.90.md) | Exposure of confidential secret or token PlanetScale password | High | Passive |
| [798.91](798.91.md) | Exposure of confidential secret or token PlanetScale API token | High | Passive |
| [798.93](798.93.md) | Exposure of confidential secret or token Postman API token | High | Passive |
| [798.94](798.94.md) | Exposure of confidential secret or token SSH private key | High | Passive |
| [798.95](798.95.md) | Exposure of confidential secret or token Pulumi API token | High | Passive |
| [798.96](798.96.md) | Exposure of confidential secret or token PyPi upload token | High | Passive |
| [798.97](798.97.md) | Exposure of confidential secret or token RubyGems API token | High | Passive |
| [798.101](798.101.md) | Exposure of confidential secret or token SendGrid API token | High | Passive |
| [798.102](798.102.md) | Exposure of confidential secret or token Brevo API token | High | Passive |
| [798.104](798.104.md) | Exposure of confidential secret or token Shippo API token | High | Passive |
| [798.105](798.105.md) | Exposure of confidential secret or token Shopify personal access token | High | Passive |
| [798.106](798.106.md) | Exposure of confidential secret or token Shopify custom app access token | High | Passive |
| [798.107](798.107.md) | Exposure of confidential secret or token Shopify private app access token | High | Passive |
| [798.108](798.108.md) | Exposure of confidential secret or token Shopify shared secret | High | Passive |
| [798.109](798.109.md) | Exposure of confidential secret or token Slack bot user OAuth token | High | Passive |
| [798.110](798.110.md) | Exposure of confidential secret or token Slack webhook | High | Passive |
| [798.111](798.111.md) | Exposure of confidential secret or token Stripe live secret key | High | Passive |
| [798.117](798.117.md) | Exposure of confidential secret or token Twilio API key | High | Passive |
| [798.118](798.118.md) | Exposure of confidential secret or token Twitch OAuth client secret | High | Passive |
| [798.121](798.121.md) | Exposure of confidential secret or token X token | High | Passive |
| [798.124](798.124.md) | Exposure of confidential secret or token Typeform personal access token | High | Passive |
| [798.130](798.130.md) | Exposure of confidential secret or token Anthropic API key | High | Passive |
| [798.131](798.131.md) | Exposure of confidential secret or token CircleCI access token | High | Passive |
| [798.132](798.132.md) | Exposure of confidential secret or token CircleCI Personal Access Token | High | Passive |
| [798.133](798.133.md) | Exposure of confidential secret or token Contentful preview API token | High | Passive |
| [798.134](798.134.md) | Exposure of confidential secret or token Contentful personal access token | High | Passive |
| [798.135](798.135.md) | Exposure of confidential secret or token DigitalOcean OAuth access token | High | Passive |
| [798.136](798.136.md) | Exposure of confidential secret or token DigitalOcean personal access token | High | Passive |
| [798.137](798.137.md) | Exposure of confidential secret or token DigitalOcean refresh token | High | Passive |
| [798.138](798.138.md) | Exposure of confidential secret or token GCP OAuth client secret | High | Passive |
| [798.139](798.139.md) | Exposure of confidential secret or token Google (GCP) service account | High | Passive |
| [798.140](798.140.md) | Exposure of confidential secret or token GitLab Personal Access Token (routable) | High | Passive |
| [798.141](798.141.md) | Exposure of confidential secret or token GitLab Personal Access Token (routable) | High | Passive |
| [798.142](798.142.md) | Exposure of confidential secret or token GitLab Pipeline trigger token | High | Passive |
| [798.143](798.143.md) | Exposure of confidential secret or token GitLab Runner registration token | High | Passive |
| [798.144](798.144.md) | Exposure of confidential secret or token GitLab Runner authentication token | High | Passive |
| [798.145](798.145.md) | Exposure of confidential secret or token GitLab Feed token | High | Passive |
| [798.146](798.146.md) | Exposure of confidential secret or token GitLab OAuth application secret | High | Passive |
| [798.147](798.147.md) | Exposure of confidential secret or token GitLab feed token v2 | High | Passive |
| [798.148](798.148.md) | Exposure of confidential secret or token GitLab Kubernetes agent token | High | Passive |
| [798.149](798.149.md) | Exposure of confidential secret or token GitLab incoming email token | High | Passive |
| [798.150](798.150.md) | Exposure of confidential secret or token GitLab deploy token | High | Passive |
| [798.151](798.151.md) | Exposure of confidential secret or token GitLab SCIM OAuth token | High | Passive |
| [798.152](798.152.md) | Exposure of confidential secret or token GitLab CI build token | High | Passive |
| [798.153](798.153.md) | Exposure of confidential secret or token Grafana API token | High | Passive |
| [798.154](798.154.md) | Exposure of confidential secret or token HashiCorp Vault batch token | High | Passive |
| [798.155](798.155.md) | Exposure of confidential secret or token Instagram access token | High | Passive |
| [798.156](798.156.md) | Exposure of confidential secret or token Intercom client secret or client ID | High | Passive |
| [798.157](798.157.md) | Exposure of confidential secret or token Ionic personal access token | High | Passive |
| [798.158](798.158.md) | Exposure of confidential secret or token Artifactory API Key | High | Passive |
| [798.159](798.159.md) | Exposure of confidential secret or token Artifactory Identity Token | High | Passive |
| [798.160](798.160.md) | Exposure of confidential secret or token MaxMind License Key | High | Passive |
| [798.161](798.161.md) | Exposure of confidential secret or token Meta access token | High | Passive |
| [798.162](798.162.md) | Exposure of confidential secret or token Oculus access token | High | Passive |
| [798.163](798.163.md) | Exposure of confidential secret or token Onfido Live API Token | High | Passive |
| [798.164](798.164.md) | Exposure of confidential secret or token OpenAI API key | High | Passive |
| [798.165](798.165.md) | Exposure of confidential secret or token Password in URL | High | Passive |
| [798.166](798.166.md) | Exposure of confidential secret or token PGP private key | High | Passive |
| [798.167](798.167.md) | Exposure of confidential secret or token PKCS8 private key | High | Passive |
| [798.168](798.168.md) | Exposure of confidential secret or token RSA private key | High | Passive |
| [798.169](798.169.md) | Exposure of confidential secret or token Segment public API token | High | Passive |
| [798.170](798.170.md) | Exposure of confidential secret or token Brevo SMTP token | High | Passive |
| [798.171](798.171.md) | Exposure of confidential secret or token Shippo Test API token | High | Passive |
| [798.172](798.172.md) | Exposure of confidential secret or token Slack app level token | High | Passive |
| [798.173](798.173.md) | Exposure of confidential secret or token SSH (DSA) private key | High | Passive |
| [798.174](798.174.md) | Exposure of confidential secret or token SSH (EC) private key | High | Passive |
| [798.175](798.175.md) | Exposure of confidential secret or token Stripe live restricted key | High | Passive |
| [798.176](798.176.md) | Exposure of confidential secret or token Stripe publishable live key | High | Passive |
| [798.177](798.177.md) | Exposure of confidential secret or token Stripe secret test key | High | Passive |
| [798.178](798.178.md) | Exposure of confidential secret or token Stripe restricted test key | High | Passive |
| [798.179](798.179.md) | Exposure of confidential secret or token Stripe publishable test key | High | Passive |
| [798.180](798.180.md) | Exposure of confidential secret or token Tailscale key | High | Passive |
| [798.181](798.181.md) | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-1 | High | Passive |
| [798.182](798.182.md) | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-2 | High | Passive |
| [798.183](798.183.md) | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-3 | High | Passive |
| [798.184](798.184.md) | Exposure of confidential secret or token Yandex Cloud AWS API compatible access secret | High | Passive |
| [829.1](829.1.md) | Inclusion of Functionality from Untrusted Control Sphere | Low | Passive |
| [829.2](829.2.md) | Invalid Sub-Resource Integrity values detected | Medium | Passive |
## Active Checks
| ID | Check | Severity | Type |
|:---|:------|:---------|:-----|
| [113.1](113.1.md) | Improper Neutralization of CRLF Sequences in HTTP Headers | High | Active |
| [1336.1](1336.1.md) | Server-Side Template Injection | High | Active |
| [16.11](16.11.md) | TRACE HTTP method enabled | High | Active |
| [22.1](22.1.md) | Improper limitation of a pathname to a restricted directory (Path traversal) | High | Active |
| [611.1](611.1.md) | External XML Entity Injection (XXE) | High | Active |
| [74.1](74.1.md) | XSLT Injection | High | Active |
| [78.1](78.1.md) | OS Command Injection | High | Active |
| [79.1](79.1.md) | Cross Site Scripting | High | Active |
| [89.1](89.1.md) | SQL Injection | High | Active |
| [917.1](917.1.md) | Expression Language Injection | High | Active |
| [918.1](918.1.md) | Server-Side Request Forgery | High | Active |
| [94.1](94.1.md) | Server-side code injection (PHP) | High | Active |
| [94.2](94.2.md) | Server-side code injection (Ruby) | High | Active |
| [94.3](94.3.md) | Server-side code injection (Python) | High | Active |
| [94.4](94.4.md) | Server-side code injection (NodeJS) | High | Active |
| [943.1](943.1.md) | Improper neutralization of special elements in data query logic | High | Active |
| [98.1](98.1.md) | PHP Remote File Inclusion | High | Active |
|
---
stage: Application Security Testing
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
title: DAST browser-based crawler vulnerability checks
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
<!--
This file is autogenerated. Do not edit directly.
See: https://gitlab.com/gitlab-org/security-products/dast-cwe-checks/-/blob/main/doc/how-to-generate-the-markdown-documentation.md
-->
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
The [DAST browser-based crawler](../_index.md) provides vulnerability checks that are used to
scan for vulnerabilities in the site under test.
## Passive Checks
| ID | Check | Severity | Type |
|:----------------------|:---------------------------------------------------------------------------------------------------------------|:---------|:-----|
| [1004.1](1004.1.md) | Sensitive cookie without HttpOnly attribute | Low | Passive |
| [16.1](16.1.md) | Missing Content-Type header | Low | Passive |
| [16.10](16.10.md) | Content-Security-Policy violations | Info | Passive |
| [16.2](16.2.md) | Server header exposes version information | Low | Passive |
| [16.3](16.3.md) | X-Powered-By header exposes version information | Low | Passive |
| [16.4](16.4.md) | X-Backend-Server header exposes server information | Info | Passive |
| [16.5](16.5.md) | AspNet header exposes version information | Low | Passive |
| [16.6](16.6.md) | AspNetMvc header exposes version information | Low | Passive |
| [16.7](16.7.md) | Strict-Transport-Security header missing or invalid | Low | Passive |
| [16.8](16.8.md) | Content-Security-Policy analysis | Info | Passive |
| [16.9](16.9.md) | Content-Security-Policy-Report-Only analysis | Info | Passive |
| [200.1](200.1.md) | Exposure of sensitive information to an unauthorized actor (private IP address) | Low | Passive |
| [209.1](209.1.md) | Generation of error message containing sensitive information | Low | Passive |
| [209.2](209.2.md) | Generation of database error message containing sensitive information | Low | Passive |
| [287.1](287.1.md) | Insecure authentication over HTTP (Basic Authentication) | Medium | Passive |
| [287.2](287.2.md) | Insecure authentication over HTTP (Digest Authentication) | Low | Passive |
| [319.1](319.1.md) | Mixed Content | Info | Passive |
| [352.1](352.1.md) | Absence of anti-CSRF tokens | Medium | Passive |
| [359.1](359.1.md) | Exposure of Private Personal Information (PII) to an unauthorized actor (credit card) | Medium | Passive |
| [359.2](359.2.md) | Exposure of Private Personal Information (PII) to an unauthorized actor (United States social security number) | Medium | Passive |
| [548.1](548.1.md) | Exposure of information through directory listing | Low | Passive |
| [598.1](598.1.md) | Use of GET request method with sensitive query strings (session ID) | Medium | Passive |
| [598.2](598.2.md) | Use of GET request method with sensitive query strings (password) | Medium | Passive |
| [598.3](598.3.md) | Use of GET request method with sensitive query strings (Authorization header details) | Medium | Passive |
| [601.1](601.1.md) | URL redirection to untrusted site ('open redirect') | Low | Passive |
| [614.1](614.1.md) | Sensitive cookie without Secure attribute | Low | Passive |
| [693.1](693.1.md) | Missing X-Content-Type-Options: nosniff | Low | Passive |
| [798.2](798.2.md) | Exposure of confidential secret or token Adobe Client ID (OAuth Web) | High | Passive |
| [798.3](798.3.md) | Exposure of confidential secret or token Adobe client secret | High | Passive |
| [798.4](798.4.md) | Exposure of confidential secret or token Age secret key | High | Passive |
| [798.7](798.7.md) | Exposure of confidential secret or token Alibaba AccessKey ID | High | Passive |
| [798.8](798.8.md) | Exposure of confidential secret or token Alibaba Secret Key | High | Passive |
| [798.9](798.9.md) | Exposure of confidential secret or token Asana client ID | High | Passive |
| [798.10](798.10.md) | Exposure of confidential secret or token Asana client secret | High | Passive |
| [798.11](798.11.md) | Exposure of confidential secret or token Atlassian API token | High | Passive |
| [798.12](798.12.md) | Exposure of confidential secret or token AWS access token | High | Passive |
| [798.13](798.13.md) | Exposure of confidential secret or token Bitbucket client ID | High | Passive |
| [798.14](798.14.md) | Exposure of confidential secret or token Bitbucket client secret | High | Passive |
| [798.17](798.17.md) | Exposure of confidential secret or token Beamer API token | High | Passive |
| [798.20](798.20.md) | Exposure of confidential secret or token Clojars deploy token | High | Passive |
| [798.23](798.23.md) | Exposure of confidential secret or token Contentful delivery API token | High | Passive |
| [798.24](798.24.md) | Exposure of confidential secret or token Databricks API token | High | Passive |
| [798.26](798.26.md) | Exposure of confidential secret or token Discord API key | High | Passive |
| [798.27](798.27.md) | Exposure of confidential secret or token Discord client ID | High | Passive |
| [798.28](798.28.md) | Exposure of confidential secret or token Discord client secret | High | Passive |
| [798.29](798.29.md) | Exposure of confidential secret or token Doppler API token | High | Passive |
| [798.30](798.30.md) | Exposure of confidential secret or token Dropbox API secret/key | High | Passive |
| [798.31](798.31.md) | Exposure of confidential secret or token Dropbox long lived API token | High | Passive |
| [798.32](798.32.md) | Exposure of confidential secret or token Dropbox short lived API token | High | Passive |
| [798.34](798.34.md) | Exposure of confidential secret or token Duffel API token | High | Passive |
| [798.35](798.35.md) | Exposure of confidential secret or token Dynatrace API token | High | Passive |
| [798.36](798.36.md) | Exposure of confidential secret or token EasyPost production API key | High | Passive |
| [798.37](798.37.md) | Exposure of confidential secret or token EasyPost test API key | High | Passive |
| [798.39](798.39.md) | Exposure of confidential secret or token Facebook token | High | Passive |
| [798.40](798.40.md) | Exposure of confidential secret or token Fastly API user or automation token | High | Passive |
| [798.41](798.41.md) | Exposure of confidential secret or token Finicity client secret | High | Passive |
| [798.42](798.42.md) | Exposure of confidential secret or token Finicity API token | High | Passive |
| [798.46](798.46.md) | Exposure of confidential secret or token Flutterwave test secret key | High | Passive |
| [798.47](798.47.md) | Exposure of confidential secret or token Flutterwave test encrypted key | High | Passive |
| [798.48](798.48.md) | Exposure of confidential secret or token Frame.io API token | High | Passive |
| [798.50](798.50.md) | Exposure of confidential secret or token GoCardless API token | High | Passive |
| [798.52](798.52.md) | Exposure of confidential secret or token GitHub personal access token (classic) | High | Passive |
| [798.53](798.53.md) | Exposure of confidential secret or token GitHub OAuth Access Token | High | Passive |
| [798.54](798.54.md) | Exposure of confidential secret or token GitHub app token | High | Passive |
| [798.55](798.55.md) | Exposure of confidential secret or token GitHub refresh token | High | Passive |
| [798.56](798.56.md) | Exposure of confidential secret or token GitLab personal access token | High | Passive |
| [798.58](798.58.md) | Exposure of confidential secret or token HashiCorp Terraform API token | High | Passive |
| [798.59](798.59.md) | Exposure of confidential secret or token Heroku API key or application authorization token | High | Passive |
| [798.60](798.60.md) | Exposure of confidential secret or token HubSpot private app API token | High | Passive |
| [798.61](798.61.md) | Exposure of confidential secret or token Intercom API token | High | Passive |
| [798.66](798.66.md) | Exposure of confidential secret or token Linear API token | High | Passive |
| [798.67](798.67.md) | Exposure of confidential secret or token Linear client secret or ID (OAuth 2.0) | High | Passive |
| [798.68](798.68.md) | Exposure of confidential secret or token LinkedIn client ID | High | Passive |
| [798.69](798.69.md) | Exposure of confidential secret or token LinkedIn client secret | High | Passive |
| [798.70](798.70.md) | Exposure of confidential secret or token Lob API key | High | Passive |
| [798.72](798.72.md) | Exposure of confidential secret or token Mailchimp API key | High | Passive |
| [798.74](798.74.md) | Exposure of confidential secret or token Mailgun private API token | High | Passive |
| [798.75](798.75.md) | Exposure of confidential secret or token Mailgun webhook signing key | High | Passive |
| [798.78](798.78.md) | Exposure of confidential secret or token MessageBird access key | High | Passive |
| [798.81](798.81.md) | Exposure of confidential secret or token New Relic user API key | High | Passive |
| [798.82](798.82.md) | Exposure of confidential secret or token New Relic user API ID | High | Passive |
| [798.83](798.83.md) | Exposure of confidential secret or token New Relic ingest browser API token | High | Passive |
| [798.84](798.84.md) | Exposure of confidential secret or token npm access token | High | Passive |
| [798.90](798.90.md) | Exposure of confidential secret or token PlanetScale password | High | Passive |
| [798.91](798.91.md) | Exposure of confidential secret or token PlanetScale API token | High | Passive |
| [798.93](798.93.md) | Exposure of confidential secret or token Postman API token | High | Passive |
| [798.94](798.94.md) | Exposure of confidential secret or token SSH private key | High | Passive |
| [798.95](798.95.md) | Exposure of confidential secret or token Pulumi API token | High | Passive |
| [798.96](798.96.md) | Exposure of confidential secret or token PyPi upload token | High | Passive |
| [798.97](798.97.md) | Exposure of confidential secret or token RubyGems API token | High | Passive |
| [798.101](798.101.md) | Exposure of confidential secret or token SendGrid API token | High | Passive |
| [798.102](798.102.md) | Exposure of confidential secret or token Brevo API token | High | Passive |
| [798.104](798.104.md) | Exposure of confidential secret or token Shippo API token | High | Passive |
| [798.105](798.105.md) | Exposure of confidential secret or token Shopify personal access token | High | Passive |
| [798.106](798.106.md) | Exposure of confidential secret or token Shopify custom app access token | High | Passive |
| [798.107](798.107.md) | Exposure of confidential secret or token Shopify private app access token | High | Passive |
| [798.108](798.108.md) | Exposure of confidential secret or token Shopify shared secret | High | Passive |
| [798.109](798.109.md) | Exposure of confidential secret or token Slack bot user OAuth token | High | Passive |
| [798.110](798.110.md) | Exposure of confidential secret or token Slack webhook | High | Passive |
| [798.111](798.111.md) | Exposure of confidential secret or token Stripe live secret key | High | Passive |
| [798.117](798.117.md) | Exposure of confidential secret or token Twilio API key | High | Passive |
| [798.118](798.118.md) | Exposure of confidential secret or token Twitch OAuth client secret | High | Passive |
| [798.121](798.121.md) | Exposure of confidential secret or token X token | High | Passive |
| [798.124](798.124.md) | Exposure of confidential secret or token Typeform personal access token | High | Passive |
| [798.130](798.130.md) | Exposure of confidential secret or token Anthropic API key | High | Passive |
| [798.131](798.131.md) | Exposure of confidential secret or token CircleCI access token | High | Passive |
| [798.132](798.132.md) | Exposure of confidential secret or token CircleCI Personal Access Token | High | Passive |
| [798.133](798.133.md) | Exposure of confidential secret or token Contentful preview API token | High | Passive |
| [798.134](798.134.md) | Exposure of confidential secret or token Contentful personal access token | High | Passive |
| [798.135](798.135.md) | Exposure of confidential secret or token DigitalOcean OAuth access token | High | Passive |
| [798.136](798.136.md) | Exposure of confidential secret or token DigitalOcean personal access token | High | Passive |
| [798.137](798.137.md) | Exposure of confidential secret or token DigitalOcean refresh token | High | Passive |
| [798.138](798.138.md) | Exposure of confidential secret or token GCP OAuth client secret | High | Passive |
| [798.139](798.139.md) | Exposure of confidential secret or token Google (GCP) service account | High | Passive |
| [798.140](798.140.md) | Exposure of confidential secret or token GitLab Personal Access Token (routable) | High | Passive |
| [798.141](798.141.md) | Exposure of confidential secret or token GitLab Personal Access Token (routable) | High | Passive |
| [798.142](798.142.md) | Exposure of confidential secret or token GitLab Pipeline trigger token | High | Passive |
| [798.143](798.143.md) | Exposure of confidential secret or token GitLab Runner registration token | High | Passive |
| [798.144](798.144.md) | Exposure of confidential secret or token GitLab Runner authentication token | High | Passive |
| [798.145](798.145.md) | Exposure of confidential secret or token GitLab Feed token | High | Passive |
| [798.146](798.146.md) | Exposure of confidential secret or token GitLab OAuth application secret | High | Passive |
| [798.147](798.147.md) | Exposure of confidential secret or token GitLab feed token v2 | High | Passive |
| [798.148](798.148.md) | Exposure of confidential secret or token GitLab Kubernetes agent token | High | Passive |
| [798.149](798.149.md) | Exposure of confidential secret or token GitLab incoming email token | High | Passive |
| [798.150](798.150.md) | Exposure of confidential secret or token GitLab deploy token | High | Passive |
| [798.151](798.151.md) | Exposure of confidential secret or token GitLab SCIM OAuth token | High | Passive |
| [798.152](798.152.md) | Exposure of confidential secret or token GitLab CI build token | High | Passive |
| [798.153](798.153.md) | Exposure of confidential secret or token Grafana API token | High | Passive |
| [798.154](798.154.md) | Exposure of confidential secret or token HashiCorp Vault batch token | High | Passive |
| [798.155](798.155.md) | Exposure of confidential secret or token Instagram access token | High | Passive |
| [798.156](798.156.md) | Exposure of confidential secret or token Intercom client secret or client ID | High | Passive |
| [798.157](798.157.md) | Exposure of confidential secret or token Ionic personal access token | High | Passive |
| [798.158](798.158.md) | Exposure of confidential secret or token Artifactory API Key | High | Passive |
| [798.159](798.159.md) | Exposure of confidential secret or token Artifactory Identity Token | High | Passive |
| [798.160](798.160.md) | Exposure of confidential secret or token MaxMind License Key | High | Passive |
| [798.161](798.161.md) | Exposure of confidential secret or token Meta access token | High | Passive |
| [798.162](798.162.md) | Exposure of confidential secret or token Oculus access token | High | Passive |
| [798.163](798.163.md) | Exposure of confidential secret or token Onfido Live API Token | High | Passive |
| [798.164](798.164.md) | Exposure of confidential secret or token OpenAI API key | High | Passive |
| [798.165](798.165.md) | Exposure of confidential secret or token Password in URL | High | Passive |
| [798.166](798.166.md) | Exposure of confidential secret or token PGP private key | High | Passive |
| [798.167](798.167.md) | Exposure of confidential secret or token PKCS8 private key | High | Passive |
| [798.168](798.168.md) | Exposure of confidential secret or token RSA private key | High | Passive |
| [798.169](798.169.md) | Exposure of confidential secret or token Segment public API token | High | Passive |
| [798.170](798.170.md) | Exposure of confidential secret or token Brevo SMTP token | High | Passive |
| [798.171](798.171.md) | Exposure of confidential secret or token Shippo Test API token | High | Passive |
| [798.172](798.172.md) | Exposure of confidential secret or token Slack app level token | High | Passive |
| [798.173](798.173.md) | Exposure of confidential secret or token SSH (DSA) private key | High | Passive |
| [798.174](798.174.md) | Exposure of confidential secret or token SSH (EC) private key | High | Passive |
| [798.175](798.175.md) | Exposure of confidential secret or token Stripe live restricted key | High | Passive |
| [798.176](798.176.md) | Exposure of confidential secret or token Stripe publishable live key | High | Passive |
| [798.177](798.177.md) | Exposure of confidential secret or token Stripe secret test key | High | Passive |
| [798.178](798.178.md) | Exposure of confidential secret or token Stripe restricted test key | High | Passive |
| [798.179](798.179.md) | Exposure of confidential secret or token Stripe publishable test key | High | Passive |
| [798.180](798.180.md) | Exposure of confidential secret or token Tailscale key | High | Passive |
| [798.181](798.181.md) | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-1 | High | Passive |
| [798.182](798.182.md) | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-2 | High | Passive |
| [798.183](798.183.md) | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-3 | High | Passive |
| [798.184](798.184.md) | Exposure of confidential secret or token Yandex Cloud AWS API compatible access secret | High | Passive |
| [829.1](829.1.md) | Inclusion of Functionality from Untrusted Control Sphere | Low | Passive |
| [829.2](829.2.md) | Invalid Sub-Resource Integrity values detected | Medium | Passive |
## Active Checks
| ID | Check | Severity | Type |
|:---|:------|:---------|:-----|
| [113.1](113.1.md) | Improper Neutralization of CRLF Sequences in HTTP Headers | High | Active |
| [1336.1](1336.1.md) | Server-Side Template Injection | High | Active |
| [16.11](16.11.md) | TRACE HTTP method enabled | High | Active |
| [22.1](22.1.md) | Improper limitation of a pathname to a restricted directory (Path traversal) | High | Active |
| [611.1](611.1.md) | External XML Entity Injection (XXE) | High | Active |
| [74.1](74.1.md) | XSLT Injection | High | Active |
| [78.1](78.1.md) | OS Command Injection | High | Active |
| [79.1](79.1.md) | Cross Site Scripting | High | Active |
| [89.1](89.1.md) | SQL Injection | High | Active |
| [917.1](917.1.md) | Expression Language Injection | High | Active |
| [918.1](918.1.md) | Server-Side Request Forgery | High | Active |
| [94.1](94.1.md) | Server-side code injection (PHP) | High | Active |
| [94.2](94.2.md) | Server-side code injection (Ruby) | High | Active |
| [94.3](94.3.md) | Server-side code injection (Python) | High | Active |
| [94.4](94.4.md) | Server-side code injection (NodeJS) | High | Active |
| [943.1](943.1.md) | Improper neutralization of special elements in data query logic | High | Active |
| [98.1](98.1.md) | PHP Remote File Inclusion | High | Active |
|
https://docs.gitlab.com/user/application_security/dast/browser/693.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/693.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
693.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Missing X-Content-Type-Options: nosniff
| null |
## Description
The `X-Content-Type-Options` header with the value `nosniff` ensures that user agents do not attempt to
guess the format of the data being received. User Agents such as browsers, commonly attempt to guess
what the resource type being requested is, through a process called MIME type sniffing.
Without this header being sent, the browser may misinterpret the data, leading to MIME confusion attacks.
If an attacker were able to upload files that are accessible by using a browser, they could upload files
that could be interpreted as HTML and execute Cross-Site Scripting (XSS) attacks.
## Remediation
We recommend that the header and value of `X-Content-Type-Options: nosniff` be set server wide.
This ensures any resources that are mistakenly missing a `Content-Type` value are not
misinterpreted.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 693.1 | true | 693 | Passive | Low |
## Links
- [OWASP](https://owasp.org/www-project-secure-headers/#x-content-type-options)
- [CWE](https://cwe.mitre.org/data/definitions/693.html)
- [Mozilla Blog on MIME Confusion attacks](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
- [Mozilla MDN on X-Content-Type-Options](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options)
|
---
stage: Application Security Testing
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
title: 'Missing X-Content-Type-Options: nosniff'
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The `X-Content-Type-Options` header with the value `nosniff` ensures that user agents do not attempt to
guess the format of the data being received. User Agents such as browsers, commonly attempt to guess
what the resource type being requested is, through a process called MIME type sniffing.
Without this header being sent, the browser may misinterpret the data, leading to MIME confusion attacks.
If an attacker were able to upload files that are accessible by using a browser, they could upload files
that could be interpreted as HTML and execute Cross-Site Scripting (XSS) attacks.
## Remediation
We recommend that the header and value of `X-Content-Type-Options: nosniff` be set server wide.
This ensures any resources that are mistakenly missing a `Content-Type` value are not
misinterpreted.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 693.1 | true | 693 | Passive | Low |
## Links
- [OWASP](https://owasp.org/www-project-secure-headers/#x-content-type-options)
- [CWE](https://cwe.mitre.org/data/definitions/693.html)
- [Mozilla Blog on MIME Confusion attacks](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
- [Mozilla MDN on X-Content-Type-Options](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.108
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.108.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.108.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Shopify shared secret
| null |
## Description
The response body contains content that matches the pattern of a Shopify shared secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.108 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Shopify shared secret
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Shopify shared secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.108 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.174
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.174.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.174.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token SSH (EC) private key
| null |
## Description
The response body contains content that matches the pattern of an SSH private key was identified. Private SSH keys are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To generate a new ECDSA key, use the `ssh-keygen` tool:
```console ssh-keygen -t ecdsa```
Note: Newer versions of SSH may output `-----BEGIN OPENSSH PRIVATE KEY-----` instead of `-----BEGIN EC PRIVATE KEY-----`
For more information, please see the [`ssh-keygen` documentation](https://linux.die.net/man/1/ssh-keygen).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.174 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token SSH (EC) private key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an SSH private key was identified. Private SSH keys are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To generate a new ECDSA key, use the `ssh-keygen` tool:
```console ssh-keygen -t ecdsa```
Note: Newer versions of SSH may output `-----BEGIN OPENSSH PRIVATE KEY-----` instead of `-----BEGIN EC PRIVATE KEY-----`
For more information, please see the [`ssh-keygen` documentation](https://linux.die.net/man/1/ssh-keygen).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.174 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.172
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.172.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.172.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Slack app level token
| null |
## Description
The response body contains content that matches the pattern of a Slack app level token was identified. App level tokens are for use with Slack apps but only with specific APIs, which are related to the app across all organizations where the app is installed.
Three scope levels can be assigned:
- `connections:write:` Route your app's interactions and event payloads over WebSockets
- `authorizations:read:` View information about your app's authorizations on installed teams
- `app_configurations:write:` Configure your application
A malicious actor with access to this token is granted one or more of the above permissions to access the API with for a specific application.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Slack app level token:
- Sign in to Slack and access <https://api.slack.com/apps>
- Find the application with the identified token and select the name
- In the left-hand menu, select "Basic Information"
- Scroll down to the "App-Level Tokens" section and select the token name of the identified token
- In the token dialog, select "Revoke"
- When prompted, select "Yes, I'm sure" in the "Are you sure?" dialog
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.172 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Slack app level token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Slack app level token was identified. App level tokens are for use with Slack apps but only with specific APIs, which are related to the app across all organizations where the app is installed.
Three scope levels can be assigned:
- `connections:write:` Route your app's interactions and event payloads over WebSockets
- `authorizations:read:` View information about your app's authorizations on installed teams
- `app_configurations:write:` Configure your application
A malicious actor with access to this token is granted one or more of the above permissions to access the API with for a specific application.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Slack app level token:
- Sign in to Slack and access <https://api.slack.com/apps>
- Find the application with the identified token and select the name
- In the left-hand menu, select "Basic Information"
- Scroll down to the "App-Level Tokens" section and select the token name of the identified token
- In the token dialog, select "Revoke"
- When prompted, select "Yes, I'm sure" in the "Are you sure?" dialog
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.172 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.30
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.30.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.30.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Dropbox API secret/key
| null |
## Description
The response body contains content that matches the pattern of a Dropbox API secret/key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.30 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Dropbox API secret/key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Dropbox API secret/key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.30 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/1336.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/1336.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
1336.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Server-Side Template Injection
| null |
## Description
The application is vulnerable to Server-Side Template Injection (SSTI), which enables attackers to
manipulate templates on the server side. This vulnerability arises when untrusted user input is
directly used in server-side templates without adequate sanitization. Attackers can exploit this
weakness to inject and execute arbitrary code in templates, potentially compromising the
system's integrity and confidentiality.
## Remediation
User-controlled data should always have special elements neutralized when used as part of
constructing Expression Language statements. Consult the documentation for the template
system in use on how properly neutralize user-controlled data.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 1336.1 | false | 1336 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/1336.html)
- [Testing for Server-side Template Injection](https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/07-Input_Validation_Testing/18-Testing_for_Server-side_Template_Injection)
|
---
stage: Application Security Testing
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
title: Server-Side Template Injection
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The application is vulnerable to Server-Side Template Injection (SSTI), which enables attackers to
manipulate templates on the server side. This vulnerability arises when untrusted user input is
directly used in server-side templates without adequate sanitization. Attackers can exploit this
weakness to inject and execute arbitrary code in templates, potentially compromising the
system's integrity and confidentiality.
## Remediation
User-controlled data should always have special elements neutralized when used as part of
constructing Expression Language statements. Consult the documentation for the template
system in use on how properly neutralize user-controlled data.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 1336.1 | false | 1336 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/1336.html)
- [Testing for Server-side Template Injection](https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/07-Input_Validation_Testing/18-Testing_for_Server-side_Template_Injection)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.36
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.36.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.36.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token EasyPost production API key
| null |
## Description
The response body contains content that matches the pattern of an EasyPost production API key was identified. Production API keys are used for live application operations and allow full account access. A malicious actor with access to this token can execute all API calls for the target environment.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the identified API token:
- Sign in to your account and go to the settings page <https://www.easypost.com/account/settings>
- Under the "Production API Keys", select the "Status" checkbox to disable the key
- In the "Are you sure you want to disable this key?" dialog, select "Disable"
- In the "Status" checkbox area, select the trash can icon to delete the key
For information on revoking and handling API Key Management, please [see their documentation](https://docs.easypost.com/docs/authentication#api-key-management).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.36 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token EasyPost production API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an EasyPost production API key was identified. Production API keys are used for live application operations and allow full account access. A malicious actor with access to this token can execute all API calls for the target environment.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the identified API token:
- Sign in to your account and go to the settings page <https://www.easypost.com/account/settings>
- Under the "Production API Keys", select the "Status" checkbox to disable the key
- In the "Are you sure you want to disable this key?" dialog, select "Disable"
- In the "Status" checkbox area, select the trash can icon to delete the key
For information on revoking and handling API Key Management, please [see their documentation](https://docs.easypost.com/docs/authentication#api-key-management).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.36 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/22.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/22.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
22.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Improper limitation of a pathname to a restricted directory (Path traversal)
| null |
## Description
The vulnerability can be exploited by inserting a payload into a
parameter on the URL endpoint which allows for reading arbitrary files.
This could be used to read sensitive files, access other users data, or aid in
exploitation to gain further system access.
## Remediation
User input should never be used in constructing paths or files for interacting
with the filesystem. This includes filenames supplied by user uploads or downloads.
If possible, consider hashing the filenames and reference the hashed filenames in
a database or datastore instead of directly attempting to access filenames provided
by users or other system components.
In the rare cases that the application must work with filenames, use the language
provided functionality to extract only the filename part of the supplied value.
Never attempt to use the path or directory information that comes from user input.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 22.1 | false | 22 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/attacks/Path_Traversal)
- [CWE](https://cwe.mitre.org/data/definitions/22.html)
|
---
stage: Application Security Testing
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
title: Improper limitation of a pathname to a restricted directory (Path traversal)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The vulnerability can be exploited by inserting a payload into a
parameter on the URL endpoint which allows for reading arbitrary files.
This could be used to read sensitive files, access other users data, or aid in
exploitation to gain further system access.
## Remediation
User input should never be used in constructing paths or files for interacting
with the filesystem. This includes filenames supplied by user uploads or downloads.
If possible, consider hashing the filenames and reference the hashed filenames in
a database or datastore instead of directly attempting to access filenames provided
by users or other system components.
In the rare cases that the application must work with filenames, use the language
provided functionality to extract only the filename part of the supplied value.
Never attempt to use the path or directory information that comes from user input.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 22.1 | false | 22 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/attacks/Path_Traversal)
- [CWE](https://cwe.mitre.org/data/definitions/22.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.138
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.138.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.138.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GCP OAuth client secret
| null |
## Description
The response body contains content that matches the pattern of a GCP OAuth client secret was identified. Client secret are used when allowing users to Sign in to your application. Depending on the scopes requested, a malicious actor with access to the secret can impersonate the service to access users information.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the OAuth client secret:
- Sign in to your GCP account and go to <https://console.cloud.google.com/apis/credentials>
- Under the "Name" column of "OAuth 2.0 Client IDs" table, select the name of the client of the identified key
- Under the "Client secrets" section, you must first add a new secret, select "Add Secret"
- For the identified key, select "Disable"
- When prompted, select "Disable" in the "Disable this secret?" dialog
- You may now select the trash icon to delete the disabled key
For more information, please see [Googles authentication documentation on setting up OAuth 2.0](https://support.google.com/cloud/answer/6158849?hl=en)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.138 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GCP OAuth client secret
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GCP OAuth client secret was identified. Client secret are used when allowing users to Sign in to your application. Depending on the scopes requested, a malicious actor with access to the secret can impersonate the service to access users information.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the OAuth client secret:
- Sign in to your GCP account and go to <https://console.cloud.google.com/apis/credentials>
- Under the "Name" column of "OAuth 2.0 Client IDs" table, select the name of the client of the identified key
- Under the "Client secrets" section, you must first add a new secret, select "Add Secret"
- For the identified key, select "Disable"
- When prompted, select "Disable" in the "Disable this secret?" dialog
- You may now select the trash icon to delete the disabled key
For more information, please see [Googles authentication documentation on setting up OAuth 2.0](https://support.google.com/cloud/answer/6158849?hl=en)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.138 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.144
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.144.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.144.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GitLab runner authentication token
| null |
## Description
The response body contains content that matches the pattern of a GitLab Runner authentication token was identified. These tokens allow users to register or authenticate as a runner with the selected project. A malicious actor with access to this token can add a custom runner to the pipeline and possibly compromise the repository if the runner was used.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a runner authentication token, the runner needs to be removed and re-created:
- Sign in to your GitLab account and visit the project that created the runner registration token
- In the left-hand menu, select "Settings"
- Under the "Settings" options, select "CI/CD"
- Under the "Runners" section, find the runner with the identified token, (you can check the runner `config.toml` if you are unsure)
- Select "Remove runner"
- When prompted, select "Remove"
For more information, please see [GitLabs documentation on registering runners](https://docs.gitlab.com/runner/register/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.144 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GitLab runner authentication token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GitLab Runner authentication token was identified. These tokens allow users to register or authenticate as a runner with the selected project. A malicious actor with access to this token can add a custom runner to the pipeline and possibly compromise the repository if the runner was used.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a runner authentication token, the runner needs to be removed and re-created:
- Sign in to your GitLab account and visit the project that created the runner registration token
- In the left-hand menu, select "Settings"
- Under the "Settings" options, select "CI/CD"
- Under the "Runners" section, find the runner with the identified token, (you can check the runner `config.toml` if you are unsure)
- Select "Remove runner"
- When prompted, select "Remove"
For more information, please see [GitLabs documentation on registering runners](https://docs.gitlab.com/runner/register/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.144 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.142
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.142.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.142.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GitLab pipeline trigger token
| null |
## Description
The response body contains content that matches the pattern of a GitLab pipeline trigger token was identified. Pipeline trigger tokens can be used to execute pipelines for a branch or tag of a project. The token impersonates a user's project access and permissions. A malicious actor with access to this token can execute pipelines with custom variables, potentially being able to compromise the repository.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a pipeline trigger token:
- Sign in to your GitLab account and visit the project that created the pipeline trigger token
- In the left-hand menu, select "Settings"
- Under the "Settings" options, select "CI/CD"
- Under the "Pipeline trigger tokens" section find the identified token
- Select the trash icon in the "Actions" column of the "Active pipeline trigger tokens" table
- When prompted, select "Revoke trigger"
For more information, please see [GitLabs documentation on pipeline trigger tokens](../../../../../ci/triggers/_index.md#create-a-pipeline-trigger-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.142 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GitLab pipeline trigger token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GitLab pipeline trigger token was identified. Pipeline trigger tokens can be used to execute pipelines for a branch or tag of a project. The token impersonates a user's project access and permissions. A malicious actor with access to this token can execute pipelines with custom variables, potentially being able to compromise the repository.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a pipeline trigger token:
- Sign in to your GitLab account and visit the project that created the pipeline trigger token
- In the left-hand menu, select "Settings"
- Under the "Settings" options, select "CI/CD"
- Under the "Pipeline trigger tokens" section find the identified token
- Select the trash icon in the "Actions" column of the "Active pipeline trigger tokens" table
- When prompted, select "Revoke trigger"
For more information, please see [GitLabs documentation on pipeline trigger tokens](../../../../../ci/triggers/_index.md#create-a-pipeline-trigger-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.142 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.20
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.20.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.20.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Clojars deploy token
| null |
## Description
The response body contains content that matches the pattern of a Clojars deploy token was detected. A deploy token is used in place of a password when deploying, and cannot be used to sign in. Tokens can be scoped to:
- Any artifact you have access to ("*")
- Any artifact in a group you have access to ("group-name/*")
- A particular artifact you have access to ("group-name/artifact-name") A malicious actor with access to this token can deploy malicious Clojure JARs by using this account.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a deploy token:
1. Visit <https://clojars.org/tokens> after logging in.
1. Under "Existing Deploy Tokens" find the token that was detected
1. Select "Disable token".
{{< alert type="note" >}}
It's not possible to re-enable the token after disabling it.
{{< /alert >}}
To create a new deploy token:
1. Visit <https://clojars.org/tokens> after logging in.
1. Fill out the Token name 1. Select the appropriate token scope
1. If the token is a single use, select the "Single use?" check box, otherwise leave blank
1. Set an expiration date (90 days is recommended)
1. Select "Create Token" For more information on tokens, please see [Clojars website](https://github.com/clojars/clojars-web/wiki/Deploy-Tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.20 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Clojars deploy token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Clojars deploy token was detected. A deploy token is used in place of a password when deploying, and cannot be used to sign in. Tokens can be scoped to:
- Any artifact you have access to ("*")
- Any artifact in a group you have access to ("group-name/*")
- A particular artifact you have access to ("group-name/artifact-name") A malicious actor with access to this token can deploy malicious Clojure JARs by using this account.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a deploy token:
1. Visit <https://clojars.org/tokens> after logging in.
1. Under "Existing Deploy Tokens" find the token that was detected
1. Select "Disable token".
{{< alert type="note" >}}
It's not possible to re-enable the token after disabling it.
{{< /alert >}}
To create a new deploy token:
1. Visit <https://clojars.org/tokens> after logging in.
1. Fill out the Token name 1. Select the appropriate token scope
1. If the token is a single use, select the "Single use?" check box, otherwise leave blank
1. Set an expiration date (90 days is recommended)
1. Select "Create Token" For more information on tokens, please see [Clojars website](https://github.com/clojars/clojars-web/wiki/Deploy-Tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.20 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.26
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.26.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.26.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Discord API key
| null |
## Description
The response body contains content that matches the pattern of a Discord API key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.26 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Discord API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Discord API key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.26 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/287.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/287.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
287.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Insecure authentication over HTTP (Basic Authentication)
| null |
## Description
The target application was found to authenticate users using the Basic Authentication scheme over HTTP.
Basic Authentication base64 encodes the username and password and sends it in the `Authentication` header.
Attackers who are in between the communication path (or on the same local network) of the client and server
could use packet sniffers to read and decode the username and password.
## Remediation
If possible, switch to a more robust method to authenticate users such as OAuth 2.0, or storing usernames
and passwords in a data store protected by the Argon2id algorithm. If Basic Authentication must be used,
ensure credentials are only transmitted over secure channels such as HTTPS/TLS.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 287.1 | false | 287 | Passive | Medium |
## Links
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html)
- [OAuth 2.0](https://oauth.net/2/)
- [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- [RFC](https://datatracker.ietf.org/doc/html/rfc7617)
|
---
stage: Application Security Testing
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
title: Insecure authentication over HTTP (Basic Authentication)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The target application was found to authenticate users using the Basic Authentication scheme over HTTP.
Basic Authentication base64 encodes the username and password and sends it in the `Authentication` header.
Attackers who are in between the communication path (or on the same local network) of the client and server
could use packet sniffers to read and decode the username and password.
## Remediation
If possible, switch to a more robust method to authenticate users such as OAuth 2.0, or storing usernames
and passwords in a data store protected by the Argon2id algorithm. If Basic Authentication must be used,
ensure credentials are only transmitted over secure channels such as HTTPS/TLS.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 287.1 | false | 287 | Passive | Medium |
## Links
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html)
- [OAuth 2.0](https://oauth.net/2/)
- [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- [RFC](https://datatracker.ietf.org/doc/html/rfc7617)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.154
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.154.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.154.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token HashiCorp Vault batch token
| null |
## Description
The response body contains content that matches the pattern of a HashiCorp Vault batch token was identified. Batch tokens are used when hundreds to thousands of systems need to access Vault but generating unique tokens would not scale. These tokens are usually short lived and bound to a specific vault policy. A malicious actor with access to this token can impersonate a service and would have the same permission levels as the policy that the batch token is created for.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). Batch tokens cannot be revoked so you should use very short "time to live" values when creating batch tokens. For more information, please see [Vault's documentation on batch tokens](https://developer.hashicorp.com/vault/tutorials/tokens/batch-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.154 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token HashiCorp Vault batch token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a HashiCorp Vault batch token was identified. Batch tokens are used when hundreds to thousands of systems need to access Vault but generating unique tokens would not scale. These tokens are usually short lived and bound to a specific vault policy. A malicious actor with access to this token can impersonate a service and would have the same permission levels as the policy that the batch token is created for.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). Batch tokens cannot be revoked so you should use very short "time to live" values when creating batch tokens. For more information, please see [Vault's documentation on batch tokens](https://developer.hashicorp.com/vault/tutorials/tokens/batch-tokens).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.154 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.152
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.152.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.152.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GitLab CI build token
| null |
## Description
The response body contains content that matches the pattern of a GitLab CI build (job) token was identified. Job tokens are used to execute functionality in the context of a pipeline job. In most cases job tokens have limited privileges and can only be used to read from the repository where the pipeline executes from. External projects can grant access to job tokens from other projects. A malicious actor has a limited time frame to use this token to attempt to access the repository.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). Because job tokens are short lived, there is no revocation process, it is no longer available after the job that created it completes.
For more details on exactly what a job token is allowed to access, please see [GitLabs documentation on job tokens](../../../../../ci/jobs/ci_job_token.md).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.152 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GitLab CI build token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GitLab CI build (job) token was identified. Job tokens are used to execute functionality in the context of a pipeline job. In most cases job tokens have limited privileges and can only be used to read from the repository where the pipeline executes from. External projects can grant access to job tokens from other projects. A malicious actor has a limited time frame to use this token to attempt to access the repository.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). Because job tokens are short lived, there is no revocation process, it is no longer available after the job that created it completes.
For more details on exactly what a job token is allowed to access, please see [GitLabs documentation on job tokens](../../../../../ci/jobs/ci_job_token.md).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.152 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/611.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/611.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
611.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
External XML Entity Injection (XXE)
| null |
## Description
It is possible to cause the application's XML parser to include external resources.
This can include files or in some circumstances initiate requests to third party
servers.
## Remediation
Consult the documentation for the XML Parser used by the target application for security
guidelines and hardening steps. It is recommended that all XML parsers disable external
entity resolution and XML `xinclude` features. Most XML parsers based on `libxml` can also be
configured to disable network access.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 611.1 | false | 611 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing)
- [CWE](https://cwe.mitre.org/data/definitions/611.html)
|
---
stage: Application Security Testing
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
title: External XML Entity Injection (XXE)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
It is possible to cause the application's XML parser to include external resources.
This can include files or in some circumstances initiate requests to third party
servers.
## Remediation
Consult the documentation for the XML Parser used by the target application for security
guidelines and hardening steps. It is recommended that all XML parsers disable external
entity resolution and XML `xinclude` features. Most XML parsers based on `libxml` can also be
configured to disable network access.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 611.1 | false | 611 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing)
- [CWE](https://cwe.mitre.org/data/definitions/611.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.41
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.41.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.41.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Finicity client secret
| null |
## Description
The response body contains content that matches the pattern of a Finicity client secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.41 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Finicity client secret
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Finicity client secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.41 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/917.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/917.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
917.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Expression Language Injection
| null |
## Description
It is possible to execute arbitrary Expression Language (EL) statements on the target
application server. EL injection is a critical severity vulnerability that can lead to
full system compromise. EL injection can occur when attacker-controlled data is used to construct
EL statements without neutralizing special characters. These special characters could modify the
intended EL statement prior to it being executed by an interpreter.
## Remediation
User-controlled data should always have special elements neutralized when used as part of
constructing Expression Language statements. Please consult the documentation for the EL
interpreter in use on how properly neutralize user controlled data.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 917.1 | false | 917 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/917.html)
- [OWASP](https://owasp.org/www-community/vulnerabilities/Expression_Language_Injection)
- [Expression Language Injection [PDF]](https://mindedsecurity.com/wp-content/uploads/2020/10/ExpressionLanguageInjection.pdf)
|
---
stage: Application Security Testing
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
title: Expression Language Injection
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
It is possible to execute arbitrary Expression Language (EL) statements on the target
application server. EL injection is a critical severity vulnerability that can lead to
full system compromise. EL injection can occur when attacker-controlled data is used to construct
EL statements without neutralizing special characters. These special characters could modify the
intended EL statement prior to it being executed by an interpreter.
## Remediation
User-controlled data should always have special elements neutralized when used as part of
constructing Expression Language statements. Please consult the documentation for the EL
interpreter in use on how properly neutralize user controlled data.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 917.1 | false | 917 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/917.html)
- [OWASP](https://owasp.org/www-community/vulnerabilities/Expression_Language_Injection)
- [Expression Language Injection [PDF]](https://mindedsecurity.com/wp-content/uploads/2020/10/ExpressionLanguageInjection.pdf)
|
https://docs.gitlab.com/user/application_security/dast/browser/1004.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/1004.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
1004.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Sensitive cookie without HttpOnly attribute
| null |
## Description
The cookie was transmitted in a `Set-Cookie` header without the `HttpOnly` attribute set.
To prevent JavaScript being able to access the cookie value - usually via `document.cookies` - all
cookies that are used for authorization should have the `HttpOnly` attribute
set.
## Remediation
Most web application frameworks allow configuring how cookies are sent to user-agents. Consult your framework's
documentation for more information on how to enable various security directives when assigning cookies to clients.
If the application is assigning cookies via writing to the response headers directly, ensure all responses include
the `HttpOnly` attribute. By enabling this protection, the application is able to mitigate the impact of
certain Cross-Site Scripting (XSS) attacks.
Example:
```http
Set-Cookie: {cookie_name}=<random secure value>; HttpOnly
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 1004.1 | false | 1004 | Passive | Low |
## Links
- [OWASP](https://owasp.org/www-community/HttpOnly)
- [CWE](https://cwe.mitre.org/data/definitions/1004.html)
- [Mozilla MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies)
|
---
stage: Application Security Testing
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
title: Sensitive cookie without HttpOnly attribute
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The cookie was transmitted in a `Set-Cookie` header without the `HttpOnly` attribute set.
To prevent JavaScript being able to access the cookie value - usually via `document.cookies` - all
cookies that are used for authorization should have the `HttpOnly` attribute
set.
## Remediation
Most web application frameworks allow configuring how cookies are sent to user-agents. Consult your framework's
documentation for more information on how to enable various security directives when assigning cookies to clients.
If the application is assigning cookies via writing to the response headers directly, ensure all responses include
the `HttpOnly` attribute. By enabling this protection, the application is able to mitigate the impact of
certain Cross-Site Scripting (XSS) attacks.
Example:
```http
Set-Cookie: {cookie_name}=<random secure value>; HttpOnly
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 1004.1 | false | 1004 | Passive | Low |
## Links
- [OWASP](https://owasp.org/www-community/HttpOnly)
- [CWE](https://cwe.mitre.org/data/definitions/1004.html)
- [Mozilla MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.47
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.47.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.47.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Flutterwave test encrypted key
| null |
## Description
The response body contains content that matches the pattern of a test Flutterwave encryption key was identified. This key is only used with the [direct charge endpoint](https://developer.flutterwave.com/docs/direct-card-charge). This key is used to encrypt payloads of card details prior to sending. More information can be found in [Flutterwave's encryption guide](https://developer.flutterwave.com/docs/encryption). A malicious actor with access to this key can potentially decrypt test transactions which can include credit card information.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your key:
- Sign in and go to <https://app.flutterwave.com/dashboard/home>
- Select "Settings" on the left-hand menu
- Select "API Keys" under "Developers" on the left-hand menu
- Ensure "Test mode" is activated
- Select "Generate secret key" to rotate the public, secret, and encryption key
For more information, please see the [Flutterwave documentation on authentication](https://developer.flutterwave.com/docs/authentication).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.47 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Flutterwave test encrypted key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a test Flutterwave encryption key was identified. This key is only used with the [direct charge endpoint](https://developer.flutterwave.com/docs/direct-card-charge). This key is used to encrypt payloads of card details prior to sending. More information can be found in [Flutterwave's encryption guide](https://developer.flutterwave.com/docs/encryption). A malicious actor with access to this key can potentially decrypt test transactions which can include credit card information.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your key:
- Sign in and go to <https://app.flutterwave.com/dashboard/home>
- Select "Settings" on the left-hand menu
- Select "API Keys" under "Developers" on the left-hand menu
- Ensure "Test mode" is activated
- Select "Generate secret key" to rotate the public, secret, and encryption key
For more information, please see the [Flutterwave documentation on authentication](https://developer.flutterwave.com/docs/authentication).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.47 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.135
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.135.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.135.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token DigitalOcean OAuth access token
| null |
## Description
The response body contains content that matches the pattern of a DigitalOcean OAuth Access Token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.135 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token DigitalOcean OAuth access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a DigitalOcean OAuth Access Token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.135 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.149
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.149.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.149.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token GitLab incoming email token
| null |
## Description
The response body contains content that matches the pattern of a GitLab incoming email token was identified. Your incoming email token authenticates you when you create a new issue by email, and is included in your personal project-specific email addresses. It cannot be used to access any other data. A malicious actor with access to this token can create issues as if they were you.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To regenerate a feed token:
- Sign in to your GitLab account and access the [User settings](../../../../../user/profile/_index.md#access-your-user-settings) left-hand side menu, select "Access tokens"
- Under the "Incoming email token" section, select the "reset this token" link
- When prompted select "OK"
For more information, please see [GitLabs documentation on feed tokens](../../../../../security/tokens/_index.md#feed-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.149 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token GitLab incoming email token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a GitLab incoming email token was identified. Your incoming email token authenticates you when you create a new issue by email, and is included in your personal project-specific email addresses. It cannot be used to access any other data. A malicious actor with access to this token can create issues as if they were you.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To regenerate a feed token:
- Sign in to your GitLab account and access the [User settings](../../../../../user/profile/_index.md#access-your-user-settings) left-hand side menu, select "Access tokens"
- Under the "Incoming email token" section, select the "reset this token" link
- When prompted select "OK"
For more information, please see [GitLabs documentation on feed tokens](../../../../../security/tokens/_index.md#feed-token).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.149 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.7
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.7.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.7.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Alibaba AccessKey ID
| null |
## Description
The response body contains content that matches the pattern of a Alibaba AccessKey ID.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.7 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Alibaba AccessKey ID
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Alibaba AccessKey ID.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.7 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/16.11
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.11.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
16.11.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
TRACE HTTP method enabled
| null |
## Description
The debug TRACE method was found to be enabled on the target web server. This
HTTP method reflects HTTP request data back to the user in a response. In some circumstances
this information may include sensitive data that is applied by intermediary proxies.
## Remediation
The TRACE HTTP method is for debugging only and should not be enabled on production
sites.
For Apache based web servers, ensure the `TraceEnable` directive is either removed or set to
`off`.
For Microsoft Servers, remove the registry parameter named "EnableTraceMethod" found in the below
registry key:
- `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters`
For all other server types, consult your product's documentation on how to disable the TRACE method.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.11 | false | 16 | Active | high |
## Links
- [RFC](https://datatracker.ietf.org/doc/html/rfc9110.html#section-9.3.8)
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [Apache TraceEnable](https://httpd.apache.org/docs/2.4/mod/core.html#traceenable)
|
---
stage: Application Security Testing
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
title: TRACE HTTP method enabled
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The debug TRACE method was found to be enabled on the target web server. This
HTTP method reflects HTTP request data back to the user in a response. In some circumstances
this information may include sensitive data that is applied by intermediary proxies.
## Remediation
The TRACE HTTP method is for debugging only and should not be enabled on production
sites.
For Apache based web servers, ensure the `TraceEnable` directive is either removed or set to
`off`.
For Microsoft Servers, remove the registry parameter named "EnableTraceMethod" found in the below
registry key:
- `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters`
For all other server types, consult your product's documentation on how to disable the TRACE method.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.11 | false | 16 | Active | high |
## Links
- [RFC](https://datatracker.ietf.org/doc/html/rfc9110.html#section-9.3.8)
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [Apache TraceEnable](https://httpd.apache.org/docs/2.4/mod/core.html#traceenable)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.133
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.133.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.133.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Contentful preview API token
| null |
## Description
The response body contains content that matches the pattern of a Contentful preview API token was identified. A preview API token maintains the same behavior and parameters as the Content Delivery API (CDA), but delivers the latest drafts for entries and assets. The Content Preview API is used to display the latest version of an entry. A malicious actor with access to this token can view published and unpublished entries. For more information, please see [the Preview API documentation](https://www.contentful.com/developers/docs/references/content-preview-api/).
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the preview API token:
- Sign in and visit <https://app.contentful.com/>
- Select the gear icon in the top right corner, and then select "API Keys"
- Find the API key that was detected, and select the name in the table of API keys
- Select "Delete" in the top right corner
- When prompted, select "Delete" Note this also deletes the delivery API token.
Generating a new set of API keys is required.
For more information, please see the developer [documentation on authentication](https://www.contentful.com/developers/docs/references/authentication/#the-content-delivery-and-preview-api).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.133 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Contentful preview API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Contentful preview API token was identified. A preview API token maintains the same behavior and parameters as the Content Delivery API (CDA), but delivers the latest drafts for entries and assets. The Content Preview API is used to display the latest version of an entry. A malicious actor with access to this token can view published and unpublished entries. For more information, please see [the Preview API documentation](https://www.contentful.com/developers/docs/references/content-preview-api/).
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the preview API token:
- Sign in and visit <https://app.contentful.com/>
- Select the gear icon in the top right corner, and then select "API Keys"
- Find the API key that was detected, and select the name in the table of API keys
- Select "Delete" in the top right corner
- When prompted, select "Delete" Note this also deletes the delivery API token.
Generating a new set of API keys is required.
For more information, please see the developer [documentation on authentication](https://www.contentful.com/developers/docs/references/authentication/#the-content-delivery-and-preview-api).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.133 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/94.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/94.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
94.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Server-side code injection (PHP)
| null |
## Description
The target application was found vulnerable to code injection. A malicious actor could inject arbitrary
PHP code to be executed on the server. This could lead to a full system compromise by accessing
stored secrets, injecting code to take over accounts, or executing OS commands.
## Remediation
Never pass user input directly into functions which evaluate string data as code, such as `eval`.
There is almost no benefit of passing string values to `eval`, as such the best recommendation is
to replace the current logic with more safe implementations of dynamically evaluating logic with
user input. One alternative is to use an `array()`, storing expected user inputs in an array
key, and use that key as a look up to execute functions:
```php
$func_to_run = function()
{
print('hello world');
};
$function_map = array();
$function_map["fn"] = $func_to_run; // store additional input to function mappings here
$input = "fn";
// lookup "fn" as the key
if (array_key_exists($input, $function_map)) {
// run the $func_to_run that was stored in the "fn" array hash value.
$func = $function_map[$input];
$func();
} else {
print('invalid input');
}
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 94.1 | false | 94 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/94.html)
- [OWASP](https://owasp.org/www-community/attacks/Code_Injection)
|
---
stage: Application Security Testing
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
title: Server-side code injection (PHP)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The target application was found vulnerable to code injection. A malicious actor could inject arbitrary
PHP code to be executed on the server. This could lead to a full system compromise by accessing
stored secrets, injecting code to take over accounts, or executing OS commands.
## Remediation
Never pass user input directly into functions which evaluate string data as code, such as `eval`.
There is almost no benefit of passing string values to `eval`, as such the best recommendation is
to replace the current logic with more safe implementations of dynamically evaluating logic with
user input. One alternative is to use an `array()`, storing expected user inputs in an array
key, and use that key as a look up to execute functions:
```php
$func_to_run = function()
{
print('hello world');
};
$function_map = array();
$function_map["fn"] = $func_to_run; // store additional input to function mappings here
$input = "fn";
// lookup "fn" as the key
if (array_key_exists($input, $function_map)) {
// run the $func_to_run that was stored in the "fn" array hash value.
$func = $function_map[$input];
$func();
} else {
print('invalid input');
}
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 94.1 | false | 94 | Active | high |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/94.html)
- [OWASP](https://owasp.org/www-community/attacks/Code_Injection)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.159
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.159.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.159.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Artifactory Identity Token
| null |
## Description
The response body contains content that matches the pattern of an Artifactory Identity Token was identified. An Artifactory Identity Token allows authentication to access repositories, download artifacts, upload artifacts, and execute privileged operations within JFrog Artifactory based on the token's assigned permissions. If leaked, a malicious actor could use this token to steal proprietary code, inject compromised dependencies into the software supply chain, or potentially gain unauthorized access to connected CI/CD systems that rely on Artifactory for builds.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.159 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Artifactory Identity Token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an Artifactory Identity Token was identified. An Artifactory Identity Token allows authentication to access repositories, download artifacts, upload artifacts, and execute privileged operations within JFrog Artifactory based on the token's assigned permissions. If leaked, a malicious actor could use this token to steal proprietary code, inject compromised dependencies into the software supply chain, or potentially gain unauthorized access to connected CI/CD systems that rely on Artifactory for builds.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.159 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.169
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.169.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.169.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Segment public API token
| null |
## Description
The response body contains content that matches the pattern of a Segment Public API token was identified. The Segment Public API is used to manage your Segment workspaces and its resources. Two types of tokens match this pattern, a workspace owner token and a limited role token. In general these tokens allow callers of the API to perform read, write, and delete operations. A malicious actor with access to a workspace owner token can access all workspace data. A limited role token can access the data it was granted access to on creation.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate a Public API token:
- Sign in to your Segment account and access your workspace from <https://app.segment.com/>
- From the left-hand menu, select "Settings" and go to "Workspace settings"
- Select the "Access Management" tab in the "Workspace settings" page
- Select the "Tokens" tab under "Access Management"
- Find the key that was identified, and select it
- In the right hand side, select "Edit token" in the "Token Permissions" section
- Select "Remove token" in the top right corner
- When prompted, select "Remove Token" in the dialog
For more information, please see [Segment's documentation on their public API](https://segment.com/docs/api/public-api/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.169 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Segment public API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Segment Public API token was identified. The Segment Public API is used to manage your Segment workspaces and its resources. Two types of tokens match this pattern, a workspace owner token and a limited role token. In general these tokens allow callers of the API to perform read, write, and delete operations. A malicious actor with access to a workspace owner token can access all workspace data. A limited role token can access the data it was granted access to on creation.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate a Public API token:
- Sign in to your Segment account and access your workspace from <https://app.segment.com/>
- From the left-hand menu, select "Settings" and go to "Workspace settings"
- Select the "Access Management" tab in the "Workspace settings" page
- Select the "Tokens" tab under "Access Management"
- Find the key that was identified, and select it
- In the right hand side, select "Edit token" in the "Token Permissions" section
- Select "Remove token" in the top right corner
- When prompted, select "Remove Token" in the dialog
For more information, please see [Segment's documentation on their public API](https://segment.com/docs/api/public-api/).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.169 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.61
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.61.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.61.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Intercom API token
| null |
## Description
The response body contains content that matches the pattern of a Intercom API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.61 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Intercom API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Intercom API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.61 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/829.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/829.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
829.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Inclusion of Functionality from Untrusted Control Sphere
| null |
## Description
JavaScript or CSS source files are included from third party domains without
[Sub-Resource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity).
If an attacker were to compromise the sites hosting these third party resources, they could inject malicious
script or CSS data in an attempt to compromise users of your application. However, if SRI was applied and an
attacker attempted to modify the contents of the script, the browser would not load the script and your
applications users would be protected from the malicious alterations.
## Remediation
All identified resources should be sourced from the same domain as the target application. If this is not
possible, it is strongly recommended that all `script` tags that implement `src` values, or `link` tags
that implement the `href` values include Sub-Resource Integrity. To generate SRI integrity values the
[SRI hash](https://www.srihash.org/) tool can be used, or by running one of the following commands:
- `cat FILENAME.js | openssl dgst -sha384 -binary | openssl base64 -A`
- `shasum -b -a 384 FILENAME.js | awk '{ print $1 }' | xxd -r -p | base64`
The output of these tools must be added as additional attributes, in particular: `integrity` and either
`crossorigin=anonymous` or `crossorigin=use-credentials`.
An example of a valid SRI protected script tag can be found below:
```html
<script src="https://example.com/example-framework.js"
integrity="sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC"
crossorigin="anonymous"></script>
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 829.1 | true | 829 | Passive | Low |
## Links
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Third_Party_Javascript_Management_Cheat_Sheet.html#subresource-integrity)
- [CWE](https://cwe.mitre.org/data/definitions/829.html)
- [MDN](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity)
|
---
stage: Application Security Testing
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
title: Inclusion of Functionality from Untrusted Control Sphere
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
JavaScript or CSS source files are included from third party domains without
[Sub-Resource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity).
If an attacker were to compromise the sites hosting these third party resources, they could inject malicious
script or CSS data in an attempt to compromise users of your application. However, if SRI was applied and an
attacker attempted to modify the contents of the script, the browser would not load the script and your
applications users would be protected from the malicious alterations.
## Remediation
All identified resources should be sourced from the same domain as the target application. If this is not
possible, it is strongly recommended that all `script` tags that implement `src` values, or `link` tags
that implement the `href` values include Sub-Resource Integrity. To generate SRI integrity values the
[SRI hash](https://www.srihash.org/) tool can be used, or by running one of the following commands:
- `cat FILENAME.js | openssl dgst -sha384 -binary | openssl base64 -A`
- `shasum -b -a 384 FILENAME.js | awk '{ print $1 }' | xxd -r -p | base64`
The output of these tools must be added as additional attributes, in particular: `integrity` and either
`crossorigin=anonymous` or `crossorigin=use-credentials`.
An example of a valid SRI protected script tag can be found below:
```html
<script src="https://example.com/example-framework.js"
integrity="sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC"
crossorigin="anonymous"></script>
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 829.1 | true | 829 | Passive | Low |
## Links
- [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Third_Party_Javascript_Management_Cheat_Sheet.html#subresource-integrity)
- [CWE](https://cwe.mitre.org/data/definitions/829.html)
- [MDN](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.67
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.67.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.67.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Linear client secret or ID (OAuth 2.0)
| null |
## Description
The response body contains content that matches the pattern of an OAuth 2.0 Linear client secret or ID was identified. Client secrets are used when allowing users to sign in to your application. Depending on the scopes requested, a malicious actor could impersonate the service to access a user's information.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Linear OAuth 2.0 Client secret:
- Sign in to your account at <https://linear.app/>
- Select your organization in the top left corner and select "Preferences"
- In the left-hand menu, select "API" under "My Account"
- In the "OAuth Applications" section of the page, find the application that contains the identified key
- Select the ellipsis to the right of the application name and then select "Manage application" - Next to the "Admin Actions" select "Rotate secret
- When prompted, select "Rotate" in the "Rotate your client secret?" dialog
For more information, please see [Linear's documentation on OAuth 2.0 authentication](https://developers.linear.app/docs/oauth/authentication).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.67 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Linear client secret or ID (OAuth
2.0)
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an OAuth 2.0 Linear client secret or ID was identified. Client secrets are used when allowing users to sign in to your application. Depending on the scopes requested, a malicious actor could impersonate the service to access a user's information.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Linear OAuth 2.0 Client secret:
- Sign in to your account at <https://linear.app/>
- Select your organization in the top left corner and select "Preferences"
- In the left-hand menu, select "API" under "My Account"
- In the "OAuth Applications" section of the page, find the application that contains the identified key
- Select the ellipsis to the right of the application name and then select "Manage application" - Next to the "Admin Actions" select "Rotate secret
- When prompted, select "Rotate" in the "Rotate your client secret?" dialog
For more information, please see [Linear's documentation on OAuth 2.0 authentication](https://developers.linear.app/docs/oauth/authentication).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.67 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/352.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/352.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
352.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Absence of anti-CSRF tokens
| null |
## Description
The application failed to protect against Cross-Site Request Forgery (CSRF) by using
secure application tokens or `SameSite` cookie directives.
The vulnerability can be exploited by an attacker creating a link or form on a third
party site and tricking an authenticated victim to access them.
## Remediation
Consider setting all session cookies to have the `SameSite=Strict` attribute. However,
it should be noted that this may impact usability when sharing links across other mediums.
It is recommended that a two cookie based approach is taken, as outlined in the
[Top level navigations](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-08#section-8.8.2) section
of the RFC.
If the application is using a common framework, there is a chance that Anti-CSRF protection
is built-in but needs to be enabled. Consult your application framework documentation for
details.
If neither of these options are applicable, it is **strongly** recommended that a third party library is used.
Implementing a secure Anti-CSRF system is a significant investment and difficult to do correctly.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 352.1 | true | 352 | Passive | Medium |
## Links
- [OWASP](https://owasp.org/www-community/attacks/csrf)
- [CWE](https://cwe.mitre.org/data/definitions/352.html)
|
---
stage: Application Security Testing
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
title: Absence of anti-CSRF tokens
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The application failed to protect against Cross-Site Request Forgery (CSRF) by using
secure application tokens or `SameSite` cookie directives.
The vulnerability can be exploited by an attacker creating a link or form on a third
party site and tricking an authenticated victim to access them.
## Remediation
Consider setting all session cookies to have the `SameSite=Strict` attribute. However,
it should be noted that this may impact usability when sharing links across other mediums.
It is recommended that a two cookie based approach is taken, as outlined in the
[Top level navigations](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-08#section-8.8.2) section
of the RFC.
If the application is using a common framework, there is a chance that Anti-CSRF protection
is built-in but needs to be enabled. Consult your application framework documentation for
details.
If neither of these options are applicable, it is **strongly** recommended that a third party library is used.
Implementing a secure Anti-CSRF system is a significant investment and difficult to do correctly.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 352.1 | true | 352 | Passive | Medium |
## Links
- [OWASP](https://owasp.org/www-community/attacks/csrf)
- [CWE](https://cwe.mitre.org/data/definitions/352.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.105
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.105.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.105.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Shopify personal access token
| null |
## Description
The response body contains content that matches the pattern of a Shopify personal access token was identified. Access tokens can be given restricted scopes or be given full access to all store data. A malicious actor who gained access to this token could be able to read or modify store data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). Access tokens cannot be revoked, you must uninstall and reinstall the application. Please see [Shopify's documentation for more details](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens/generate-app-access-tokens-admin#rotating-api-credentials-for-admin-created-apps).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.105 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Shopify personal access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Shopify personal access token was identified. Access tokens can be given restricted scopes or be given full access to all store data. A malicious actor who gained access to this token could be able to read or modify store data.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). Access tokens cannot be revoked, you must uninstall and reinstall the application. Please see [Shopify's documentation for more details](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens/generate-app-access-tokens-admin#rotating-api-credentials-for-admin-created-apps).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.105 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.179
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.179.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.179.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Stripe publishable test key
| null |
## Description
The response body contains content that matches the pattern of a Stripe publishable test key was identified.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.179 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Stripe publishable test key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Stripe publishable test key was identified.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.179 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/89.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/89.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
89.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
SQL Injection
| null |
## Description
It is possible to execute arbitrary SQL commands on the target application server's
backend database.
SQL Injection is a critical vulnerability that can lead to a data or system
compromise.
## Remediation
Always use parameterized queries when issuing requests to backend database systems. In
situations where dynamic queries must be created, never use direct user input, but
instead use a map or dictionary of valid values and resolve them using a user-supplied key.
For example, some database drivers do not allow parameterized queries for `>` or `<` comparison
operators. In these cases, do not use a user-supplied `>` or `<` value, but rather have the user
supply a `gt` or `lt` value. The alphabetical values are then used to look up the `>` and `<`
values to be used in the construction of the dynamic query. The same goes for other queries where
column or table names are required but can not be parameterized.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 89.1 | false | 89 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/attacks/SQL_Injection)
- [CWE](https://cwe.mitre.org/data/definitions/89.html)
|
---
stage: Application Security Testing
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
title: SQL Injection
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
It is possible to execute arbitrary SQL commands on the target application server's
backend database.
SQL Injection is a critical vulnerability that can lead to a data or system
compromise.
## Remediation
Always use parameterized queries when issuing requests to backend database systems. In
situations where dynamic queries must be created, never use direct user input, but
instead use a map or dictionary of valid values and resolve them using a user-supplied key.
For example, some database drivers do not allow parameterized queries for `>` or `<` comparison
operators. In these cases, do not use a user-supplied `>` or `<` value, but rather have the user
supply a `gt` or `lt` value. The alphabetical values are then used to look up the `>` and `<`
values to be used in the construction of the dynamic query. The same goes for other queries where
column or table names are required but can not be parameterized.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 89.1 | false | 89 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/attacks/SQL_Injection)
- [CWE](https://cwe.mitre.org/data/definitions/89.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.71
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.71.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.71.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Lob publishable API key
| null |
## Description
The response body contains content that matches the pattern of a Lob Publishable API key was identified. Publishable API keys are only used for US verifications, international verifications, and US autocomplete requests. A malicious actor with access to this key can execute limited functions under your account.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate a Publishable API key:
- Sign in to your account and go to <https://dashboard.lob.com/>
- In the bottom left corner select the gear icon / "Settings" menu option
- Under "Settings" select the "API Keys" tab
- Identify if the key was a live or test environment key in the "Publishable API Keys" section
- Select the rotate arrow icon of the identified key
- When prompted, select "Yes" in the "Rotate Publishable API Key" dialog
For more information, please see [Lob's documentation on API keys](https://docs.lob.com/#tag/Authentication/API-Keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.71 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Lob publishable API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Lob Publishable API key was identified. Publishable API keys are only used for US verifications, international verifications, and US autocomplete requests. A malicious actor with access to this key can execute limited functions under your account.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate a Publishable API key:
- Sign in to your account and go to <https://dashboard.lob.com/>
- In the bottom left corner select the gear icon / "Settings" menu option
- Under "Settings" select the "API Keys" tab
- Identify if the key was a live or test environment key in the "Publishable API Keys" section
- Select the rotate arrow icon of the identified key
- When prompted, select "Yes" in the "Rotate Publishable API Key" dialog
For more information, please see [Lob's documentation on API keys](https://docs.lob.com/#tag/Authentication/API-Keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.71 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.96
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.96.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.96.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token PyPi upload token
| null |
## Description
The response body contains content that matches the pattern of a PyPi upload token was identified. Upload tokens are used for uploading packages for publishing Python packages. A malicious actor with access to this token can upload potentially malicious artifacts.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
It is strongly recommended to switch to OIDC Connect instead of using PyPi upload tokens. Please see [PyPi's documentation on trusted publishers](https://docs.pypi.org/trusted-publishers/).
To delete a PyPi upload token:
- Sign in to your PyPi account and visit <https://pypi.org/manage/account/>
- Scroll down to the "API tokens" section
- Find the identified token and select the "Options" dropdown list
- Select "Remove token"
- When prompted, enter your password and select "Remove API Token"
For more information, please see [PyPi's documentation on upload tokens](https://pypi.org/help/#apitoken).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:-------|:-----------|:----|:-----|:-----|
| 798.96 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token PyPi upload token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a PyPi upload token was identified. Upload tokens are used for uploading packages for publishing Python packages. A malicious actor with access to this token can upload potentially malicious artifacts.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
It is strongly recommended to switch to OIDC Connect instead of using PyPi upload tokens. Please see [PyPi's documentation on trusted publishers](https://docs.pypi.org/trusted-publishers/).
To delete a PyPi upload token:
- Sign in to your PyPi account and visit <https://pypi.org/manage/account/>
- Scroll down to the "API tokens" section
- Find the identified token and select the "Options" dropdown list
- Select "Remove token"
- When prompted, enter your password and select "Remove API Token"
For more information, please see [PyPi's documentation on upload tokens](https://pypi.org/help/#apitoken).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:-------|:-----------|:----|:-----|:-----|
| 798.96 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.90
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.90.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.90.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token PlanetScale password
| null |
## Description
The response body contains content that matches the pattern of a PlanetScale password was identified. PlanetScale passwords are used to connect to database instances. A malicious actor with access to this password can access PlanetScale managed databases..
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). For more information, please see [PlanetScale's documentation on database connection strings](https://planetscale.com/docs/concepts/connection-strings).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.90 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token PlanetScale password
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a PlanetScale password was identified. PlanetScale passwords are used to connect to database instances. A malicious actor with access to this password can access PlanetScale managed databases..
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). For more information, please see [PlanetScale's documentation on database connection strings](https://planetscale.com/docs/concepts/connection-strings).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.90 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/209.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/209.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
209.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Generation of error message containing sensitive information
| null |
## Description
The application was found to return error data such as stack traces. Depending on the data contained within the error message,
this information could be used by an attacker to conduct further attacks. While stack traces are helpful during development
and debugging, they should not be presented to users when an error occurs.
## Remediation
Applications should handle exception conditions internally and map known failure types to error codes that can be displayed
to a user. These error codes should be customized to the application and returned along with the relevant HTTP error code.
When an error occurs, the application identifies the error type or class, and displays a numerical value to the
user. Requests should also be tracked so when a user is presented with an error code, it has a corresponding request ID.
Support teams can then correlate the HTTP error, the customized error code, and the request ID in the log files to
determine the root cause of the error without leaking details to the end user.
Example of returning customized errors:
```plaintext
HTTP/1.1 500 Internal Server Error
...
Error [0004] Occurred, please contact support or re-try your request again shortly.
Request ID [a4bc91def12]
...
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 209.1 | false | 209 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/209.html)
|
---
stage: Application Security Testing
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
title: Generation of error message containing sensitive information
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The application was found to return error data such as stack traces. Depending on the data contained within the error message,
this information could be used by an attacker to conduct further attacks. While stack traces are helpful during development
and debugging, they should not be presented to users when an error occurs.
## Remediation
Applications should handle exception conditions internally and map known failure types to error codes that can be displayed
to a user. These error codes should be customized to the application and returned along with the relevant HTTP error code.
When an error occurs, the application identifies the error type or class, and displays a numerical value to the
user. Requests should also be tracked so when a user is presented with an error code, it has a corresponding request ID.
Support teams can then correlate the HTTP error, the customized error code, and the request ID in the log files to
determine the root cause of the error without leaking details to the end user.
Example of returning customized errors:
```plaintext
HTTP/1.1 500 Internal Server Error
...
Error [0004] Occurred, please contact support or re-try your request again shortly.
Request ID [a4bc91def12]
...
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 209.1 | false | 209 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/209.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.173
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.173.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.173.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token SSH (DSA) private key
| null |
## Description
The response body contains content that matches the pattern of an SSH private key was identified. Private SSH keys are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To generate a new DSA key, use the `ssh-keygen` tool:
```console ssh-keygen -t dsa```
Newer versions of SSH may output `-----BEGIN OPENSSH PRIVATE KEY-----` instead of `-----BEGIN DSA PRIVATE KEY-----`
For more information, please see the `ssh-keygen` [documentation](https://linux.die.net/man/1/ssh-keygen).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.173 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token SSH (DSA) private key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an SSH private key was identified. Private SSH keys are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To generate a new DSA key, use the `ssh-keygen` tool:
```console ssh-keygen -t dsa```
Newer versions of SSH may output `-----BEGIN OPENSSH PRIVATE KEY-----` instead of `-----BEGIN DSA PRIVATE KEY-----`
For more information, please see the `ssh-keygen` [documentation](https://linux.die.net/man/1/ssh-keygen).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.173 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.109
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.109.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.109.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Slack bot user OAuth token
| null |
## Description
The response body contains content that matches the pattern of a Slack bot user OAuth token was identified. A Slack app's capabilities and permissions are governed by the scopes it requests. A full list of permissions can be found [in Slack's scopes documentation](https://api.slack.com/scopes). A malicious actor with access to this token can execute functionality that was assigned to it.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Slack bot user OAuth token (Note: This requires all users to re-authorize your application):
- Sign in to Slack and access <https://api.slack.com/apps>
- Find the application with the identified token and select the name
- In the left-hand menu, select "OAuth & Permissions"
- Scroll down to "Revoke All OAuth Tokens" and select "Revoke tokens"
- When prompted, select "Yes, I'm sure" in the "Are you sure?" dialog
- After some time, scroll back up to the "OAuth Tokens" section and select "Reinstall to XXX", where XXX is your workspace name
For more information, please see [Slack's documentation on OAuth](https://api.slack.com/authentication/oauth-v2)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.109 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Slack bot user OAuth token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Slack bot user OAuth token was identified. A Slack app's capabilities and permissions are governed by the scopes it requests. A full list of permissions can be found [in Slack's scopes documentation](https://api.slack.com/scopes). A malicious actor with access to this token can execute functionality that was assigned to it.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke a Slack bot user OAuth token (Note: This requires all users to re-authorize your application):
- Sign in to Slack and access <https://api.slack.com/apps>
- Find the application with the identified token and select the name
- In the left-hand menu, select "OAuth & Permissions"
- Scroll down to "Revoke All OAuth Tokens" and select "Revoke tokens"
- When prompted, select "Yes, I'm sure" in the "Are you sure?" dialog
- After some time, scroll back up to the "OAuth Tokens" section and select "Reinstall to XXX", where XXX is your workspace name
For more information, please see [Slack's documentation on OAuth](https://api.slack.com/authentication/oauth-v2)
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.109 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.175
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.175.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.175.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Stripe live restricted key
| null |
## Description
The response body contains content that matches the pattern of a Stripe live restricted key was identified. Restricted keys offer greater security by only allowing read or write access to specific API resources. A malicious actor with access to this key is limited by the scope defined for the key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your Stripe live restricted key:
- Sign in to your Stripe account and access <https://dashboard.stripe.com/apikeys>
- Ensure "Test mode" is disabled
- In the "Restricted keys" section, find the key that was identified and select the ellipsis in the right-hand side
- Select "Roll key..."
- In the "Roll API key" dialog, select an expiration date, for example "now"
- Select "Roll API Key"
For more information, please see [Stripe's documentation on rotating API keys](https://docs.stripe.com/keys#rolling-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.175 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Stripe live restricted key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Stripe live restricted key was identified. Restricted keys offer greater security by only allowing read or write access to specific API resources. A malicious actor with access to this key is limited by the scope defined for the key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To rotate your Stripe live restricted key:
- Sign in to your Stripe account and access <https://dashboard.stripe.com/apikeys>
- Ensure "Test mode" is disabled
- In the "Restricted keys" section, find the key that was identified and select the ellipsis in the right-hand side
- Select "Roll key..."
- In the "Roll API key" dialog, select an expiration date, for example "now"
- Select "Roll API Key"
For more information, please see [Stripe's documentation on rotating API keys](https://docs.stripe.com/keys#rolling-keys).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.175 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.163
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.163.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.163.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Onfido Live API Token
| null |
## Description
The response body contains content that matches the pattern of an Onfido Live API Token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.163 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Onfido Live API Token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an Onfido Live API Token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.163 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.184
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.184.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.184.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Yandex Cloud AWS API compatible access secret
| null |
## Description
The response body contains content that matches the pattern of Yandex Cloud AWS API compatible Access Secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.184 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Yandex Cloud AWS API compatible access
secret
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of Yandex Cloud AWS API compatible Access Secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.184 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/16.6
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.6.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
16.6.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
AspNetMvc header exposes version information
| null |
## Description
The target website returns AspNet headers along with version information of this website. By
exposing these values attackers may attempt to identify if the target software is vulnerable to known
vulnerabilities. Or catalog known sites running particular versions to exploit in the future when a
vulnerability is identified in the particular version.
## Remediation
To remove the `X-AspNetMvc-Version` information set `MvcHandler.DisableMvcResponseHeader = true;` in the
`Global.asax.cs` file in the `Application_Start()` method.
```csharp
protected void Application_Start()
{
MvcHandler.DisableMvcResponseHeader = true;
}
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.6 | true | 16 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [IIS Remove Unwanted Headers](https://techcommunity.microsoft.com/t5/iis-support-blog/remove-unwanted-http-response-headers/ba-p/369710)
|
---
stage: Application Security Testing
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
title: AspNetMvc header exposes version information
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The target website returns AspNet headers along with version information of this website. By
exposing these values attackers may attempt to identify if the target software is vulnerable to known
vulnerabilities. Or catalog known sites running particular versions to exploit in the future when a
vulnerability is identified in the particular version.
## Remediation
To remove the `X-AspNetMvc-Version` information set `MvcHandler.DisableMvcResponseHeader = true;` in the
`Global.asax.cs` file in the `Application_Start()` method.
```csharp
protected void Application_Start()
{
MvcHandler.DisableMvcResponseHeader = true;
}
```
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 16.6 | true | 16 | Passive | Low |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/16.html)
- [IIS Remove Unwanted Headers](https://techcommunity.microsoft.com/t5/iis-support-blog/remove-unwanted-http-response-headers/ba-p/369710)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.165
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.165.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.165.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token password in URL
| null |
## Description
The response body contains content that matches the pattern of a password in URL.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.165 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token password in URL
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a password in URL.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.165 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.182
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.182.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.182.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Yandex Cloud IAM cookie v1-2
| null |
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM Token v1.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.182 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Yandex Cloud IAM cookie v1-2
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM Token v1.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.182 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.17
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.17.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.17.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Beamer API token
| null |
## Description
The response body contains content that matches the pattern of a Beamer API token was detected. Beamer API tokens can be used to read, write, and delete posts, and "ideas" as well as see NPS analytical reports. This service is used to notify users of changes to your software with email or other methods. A malicious actor with access to this token can call API endpoints and create or delete posts and ideas or view reports.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). To delete your Beamer API token: - Sign in to your Beamer account at: <https://app.getbeamer.com/auth/login> - Select the gear icon ("Settings) in the bottom left corner and then select "API" in the left hand menu, or go to <https://app.getbeamer.com/settings#api> - Find the key that was detected and select the pencil icon "Edit" - Make note of all the permissions and their settings - Select "Delete Key" - Select "Create New API Key" - Apply the same settings as the detected key
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.17 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Beamer API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Beamer API token was detected. Beamer API tokens can be used to read, write, and delete posts, and "ideas" as well as see NPS analytical reports. This service is used to notify users of changes to your software with email or other methods. A malicious actor with access to this token can call API endpoints and create or delete posts and ideas or view reports.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). To delete your Beamer API token: - Sign in to your Beamer account at: <https://app.getbeamer.com/auth/login> - Select the gear icon ("Settings) in the bottom left corner and then select "API" in the left hand menu, or go to <https://app.getbeamer.com/settings#api> - Find the key that was detected and select the pencil icon "Edit" - Make note of all the permissions and their settings - Select "Delete Key" - Select "Create New API Key" - Apply the same settings as the detected key
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.17 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.11
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.11.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.11.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Atlassian API token
| null |
## Description
The response body contains content that matches the pattern of a Atlassian API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.11 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Atlassian API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Atlassian API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.11 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.27
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.27.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.27.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Discord client ID
| null |
## Description
The response body contains content that matches the pattern of a Discord client ID was identified. Client IDs are used in OAuth applications and are used in combination with a client secret. This value alone does not grant any access and must be used alongside the client secret value.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). You cannot revoke a Discord client ID. Instead you must generate an entire new Discord application.
For more information, please see [Discord's documentation on OAuth](https://discord.com/developers/docs/topics/oauth2).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.27 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Discord client ID
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Discord client ID was identified. Client IDs are used in OAuth applications and are used in combination with a client secret. This value alone does not grant any access and must be used alongside the client secret value.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet). You cannot revoke a Discord client ID. Instead you must generate an entire new Discord application.
For more information, please see [Discord's documentation on OAuth](https://discord.com/developers/docs/topics/oauth2).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.27 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.153
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.153.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.153.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Grafana API token
| null |
## Description
The response body contains content that matches the pattern of a Grafana API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.153 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Grafana API token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of a Grafana API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.153 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.155
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.155.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.155.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token Instagram access token
| null |
## Description
The response body contains content that matches the pattern of an Instagram access token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.155 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token Instagram access token
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an Instagram access token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:--------|:-----------|:----|:-----|:-----|
| 798.155 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/113.1
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/113.1.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
113.1.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Improper Neutralization of CRLF Sequences in HTTP Headers
| null |
## Description
By inserting Carriage Return / Line Feed (CRLF) characters, malicious users could potentially inject arbitrary data into HTTP responses. By modifying HTTP responses, attackers could conduct cross-site scripting or cache poisoning attacks against other users of the system.
## Remediation
User input should never be used in constructing HTTP header responses without some form
of validation against newlines. This includes URLs supplied by the user for HTTP redirects.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 113.1 | false | 113 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/attacks/HTTP_Response_Splitting)
- [CWE](https://cwe.mitre.org/data/definitions/113.html)
|
---
stage: Application Security Testing
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
title: Improper Neutralization of CRLF Sequences in HTTP Headers
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
By inserting Carriage Return / Line Feed (CRLF) characters, malicious users could potentially inject arbitrary data into HTTP responses. By modifying HTTP responses, attackers could conduct cross-site scripting or cache poisoning attacks against other users of the system.
## Remediation
User input should never be used in constructing HTTP header responses without some form
of validation against newlines. This includes URLs supplied by the user for HTTP redirects.
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 113.1 | false | 113 | Active | high |
## Links
- [OWASP](https://owasp.org/www-community/attacks/HTTP_Response_Splitting)
- [CWE](https://cwe.mitre.org/data/definitions/113.html)
|
https://docs.gitlab.com/user/application_security/dast/browser/798.37
|
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.37.md
|
2025-08-13
|
doc/user/application_security/dast/browser/checks
|
[
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] |
798.37.md
|
Application Security Testing
|
Dynamic Analysis
|
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
|
Exposure of confidential secret or token EasyPost test API key
| null |
## Description
The response body contains content that matches the pattern of an EasyPost test API key was identified. Test API keys are used for functionality testing. A malicious actor with access to this key can only use limited functionality of the EasyPost service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the identified API token:
- Sign in to your account and go to the settings page <https://www.easypost.com/account/settings>
- Under the "Test API Keys", select the "Status" checkbox to disable the key
- In the "Are you sure you want to disable this key?" dialog, select "Disable"
- In the "Status" checkbox area, select the trash can icon to delete the key
For information on revoking and handling API Key Management, please [see their documentation](https://docs.easypost.com/docs/authentication#api-key-management).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.37 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
---
stage: Application Security Testing
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
title: Exposure of confidential secret or token EasyPost test API key
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- checks
---
## Description
The response body contains content that matches the pattern of an EasyPost test API key was identified. Test API keys are used for functionality testing. A malicious actor with access to this key can only use limited functionality of the EasyPost service.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on [Credential exposure to the internet](../../../../../security/responding_to_security_incidents.md#credential-exposure-to-public-internet).
To revoke the identified API token:
- Sign in to your account and go to the settings page <https://www.easypost.com/account/settings>
- Under the "Test API Keys", select the "Status" checkbox to disable the key
- In the "Are you sure you want to disable this key?" dialog, select "Disable"
- In the "Status" checkbox area, select the trash can icon to delete the key
For information on revoking and handling API Key Management, please [see their documentation](https://docs.easypost.com/docs/authentication#api-key-management).
## Details
| ID | Aggregated | CWE | Type | Risk |
|:---|:-----------|:----|:-----|:-----|
| 798.37 | false | 798 | Passive | High |
## Links
- [CWE](https://cwe.mitre.org/data/definitions/798.html)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.