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/dast/browser/798.31 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.31.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.31.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 long lived API token | null |
## Description
The response body contains content that matches the pattern of a Dropbox long lived API token was detected. These tokens were deprecated in 2021, see <https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens#introducing-scoped-apps> for more details.
Exposing this value could allow ... | ---
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 long lived API token... |
https://docs.gitlab.com/user/application_security/dast/browser/798.143 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.143.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.143.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 registration token | null |
## Description
The response body contains content that matches the pattern of a deprecated GitLab Runner registration token was identified. These tokens allow users to register a runner with the selected project. A malicious actor with access to this token can add a custom runner to the pipeline and possibly comprom... | ---
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 registration t... |
https://docs.gitlab.com/user/application_security/dast/browser/798.139 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.139.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.139.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 Google (GCP) service account | null |
## Description
The response body contains content that matches the pattern of a GCP service account was identified. Service accounts can be assigned a wide range of permissions or access. A malicious actor with access to the service account can potentially compromise the entire GCP account or have limited access to ... | ---
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 Google (GCP) service account... |
https://docs.gitlab.com/user/application_security/dast/browser/798.145 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.145.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.145.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 feed token | null |
## Description
The response body contains content that matches the pattern of a GitLab Feed 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 d... | ---
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 feed token
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/98.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/98.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 98.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 | PHP Remote File Inclusion | null |
## Description
The server is vulnerable to PHP Remote File Inclusion (RFI), which enables attackers to load
remote files and have them executed as PHP scripts on the server side. This vulnerability occurs
when untrusted user input is directly used in script inclusion without proper validation. Attackers
can leverage... | ---
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: PHP Remote File Inclusion
breadcrumbs:
- doc
- user
- application_sec... |
https://docs.gitlab.com/user/application_security/dast/browser/16.5 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.5.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.5.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 | AspNet header exposes version information | null |
## Description
The target website returns AspNet headers and 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 ... | ---
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: AspNet header exposes version information
breadcrumbs:
- doc
- user
-... |
https://docs.gitlab.com/user/application_security/dast/browser/798.166 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.166.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.166.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 PGP private key | null |
## Description
The response body contains content that matches the pattern of a PGP private key was identified. PGP private keys are used to encrypt and decrypt messages. A malicious actor with access to this key can encrypt and decrypt all past and future messages. Note that past messages encrypted using this key s... | ---
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 PGP private key
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.181 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.181.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.181.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-1 | null |
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM Cookie 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 G... | ---
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-1... |
https://docs.gitlab.com/user/application_security/dast/browser/16.3 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.3.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.3.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 | X-Powered-By header exposes version information | null |
## Description
The target website returns the `X-Powered-By` header and 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
vu... | ---
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: X-Powered-By header exposes version information
breadcrumbs:
- doc
- ... |
https://docs.gitlab.com/user/application_security/dast/browser/798.160 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.160.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.160.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 MaxMind License Key | null |
## Description
The response body contains content that matches the pattern of a MaxMind License 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... | ---
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 MaxMind License Key
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.12 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.12.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.12.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 AWS access token | null |
## Description
The response body contains content that matches the pattern of an AWS Access Token was detected. AWS Access Tokens are usually paired along with their secret key values. A malicious actor with access to this token can access AWS services with the same permissions as the user which generated the key, p... | ---
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 AWS access token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.14 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.14.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.14.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 Bitbucket client secret | null |
## Description
The response body contains content that matches the pattern of a Bitbucket 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 Gi... | ---
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 Bitbucket client secret
brea... |
https://docs.gitlab.com/user/application_security/dast/browser/798.68 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.68.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.68.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 LinkedIn client ID | null |
## Description
The response body contains content that matches the pattern of a LinkedIn Client ID was identified. Client IDs are used in combination with a client secret. A malicious actor with access to this ID can impersonate the client application if they also have access to the client secret.
Exposing this valu... | ---
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 LinkedIn client ID
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/798.176 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.176.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.176.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 live key | null |
## Description
The response body contains content that matches the pattern of a Stripe publishable live 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... | ---
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 live key
... |
https://docs.gitlab.com/user/application_security/dast/browser/209.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/209.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 209.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 | Generation of database error message containing sensitive information | null |
## Description
The application was found to return database error messages. Determining the type of database may assist attackers in exploiting
SQL Injection attacks against the system. While debug messages are helpful during development and debugging, they should not be
presented to users when an error occurs.
## ... | ---
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 database error message containing sensitive information... |
https://docs.gitlab.com/user/application_security/dast/browser/798.170 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.170.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.170.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 SMTP token | null |
## Description
The response body contains content that matches the pattern of a Brevo SMTP 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 do... | ---
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 SMTP token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.78 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.78.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.78.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 MessageBird access key | null |
## Description
The response body contains content that matches the pattern of a MessageBird Access 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 Git... | ---
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 MessageBird access key
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/74.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/74.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 74.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 | XSLT Injection | null |
## Description
It is possible to supply an XSL template to a server-side XSLT processor. XSLT processors can
be abused to read or write files, initiate outbound connections, and in some cases execute
arbitrary code.
## Remediation
Applications should never accept user-supplied style sheets. XSLT processors are not... | ---
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: XSLT Injection
breadcrumbs:
- doc
- user
- application_security
- das... |
https://docs.gitlab.com/user/application_security/dast/browser/798.32 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.32.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.32.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 short lived API token | null |
## Description
The response body contains content that matches the pattern of a Dropbox short lived API token was detected. These tokens were deprecated in 2021, see <https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens#introducing-scoped-apps> for more details.
Exposing this value could allow... | ---
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 short lived API toke... |
https://docs.gitlab.com/user/application_security/dast/browser/798.34 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.34.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.34.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 Duffel API token | null |
## Description
The response body contains content that matches the pattern of a Duffel API token was detected. Duffel API Tokens can be either read-write or read-only depending on how they were created. A malicious actor with access to a read-write token can execute orders, book flights or hotels, or view or modify ... | ---
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 Duffel API token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.48 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.48.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.48.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 Frame.io API token | null |
## Description
The response body contains content that matches the pattern of a Frame.io API token was identified. Frame.io supports external access through scoped API tokens. Tokens are associated with individual user accounts, and have the same access permissions as the user who created them. All API actions in Fr... | ---
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 Frame.io API token
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/798.146 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.146.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.146.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 OAuth application secret | null |
## Description
The response body contains content that matches the pattern of a GitLab OAuth application secret was identified. OAuth secrets are used when allowing users to sign in to your application. Depending on the scopes assigned, a malicious actor could impersonate the service to access their repositories or ... | ---
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 OAuth application sec... |
https://docs.gitlab.com/user/application_security/dast/browser/798.8 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.8.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.8.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 Secret Key | null |
## Description
The response body contains content that matches the pattern of a Alibaba 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 ... | ---
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 Secret Key
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/798.140 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.140.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.140.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 (routable) | null |
## Description
The response body contains content that matches the pattern of a GitLab Personal Access Token (routable).
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, p... | ---
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... |
https://docs.gitlab.com/user/application_security/dast/browser/798.24 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.24.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.24.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 Databricks API token | null |
## Description
The response body contains content that matches the pattern of a Databricks 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 GitLa... | ---
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 Databricks API token
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/798.58 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.58.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.58.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 Terraform API token | null |
## Description
The response body contains content that matches the pattern of a HashiCorp Terraform API token was identified. API tokens can be used to access the HCP Terraform API. A malicious actor with access to this token can perform all actions the user account is entitled to.
Exposing this value could allow at... | ---
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 Terraform API toke... |
https://docs.gitlab.com/user/application_security/dast/browser/798.156 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.156.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.156.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 client secret or client ID | null |
## Description
The response body contains content that matches the pattern of an Intercom client secret or client 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 the user's info... | ---
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 client secret or cl... |
https://docs.gitlab.com/user/application_security/dast/browser/798.150 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.150.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.150.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 deploy token | null |
## Description
The response body contains content that matches the pattern of a GitLab deploy token was identified. A deploy token enables authentication of deployment tasks, independent of a user account. With a deploy token, automated tasks can: - Clone Git repositories - Pull from and push to a GitLab container r... | ---
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 deploy token
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.28 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.28.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.28.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 secret | null |
## Description
The response body contains content that matches the pattern of a Discord 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 GitL... | ---
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 secret
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.54 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.54.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.54.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 GitHub app token | null |
## Description
The response body contains content that matches the pattern of a GitHub App 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 do... | ---
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 GitHub app token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/94.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/94.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 94.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 | Server-side code injection (Ruby) | null |
## Description
The target application was found vulnerable to code injection. A malicious actor could inject arbitrary
Ruby 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
Neve... | ---
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 (Ruby)
breadcrumbs:
- doc
- user
- applica... |
https://docs.gitlab.com/user/application_security/dast/browser/798.52 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.52.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.52.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 GitHub personal access token (classic) | null |
## Description
The response body contains content that matches the pattern of a GitHub personal access token (classic) was identified. Personal access tokens can be used to access GitHub services as the user who created them. In most cases these tokens are given read-write access to all repositories. A malicious act... | ---
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 GitHub personal access token... |
https://docs.gitlab.com/user/application_security/dast/browser/94.4 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/94.4.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 94.4.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 (NodeJS) | null |
## Description
The target application was found vulnerable to code injection. A malicious actor could inject arbitrary
JavaScript 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... | ---
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 (NodeJS)
breadcrumbs:
- doc
- user
- appli... |
https://docs.gitlab.com/user/application_security/dast/browser/78.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/78.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 78.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 | OS Command Injection | null |
## Description
It is possible to execute arbitrary OS commands on the target application server.
OS Command Injection is a critical vulnerability that can lead to a full system
compromise.
## Remediation
User input should never be used in constructing commands or command arguments
to functions which execute OS 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: OS Command Injection
breadcrumbs:
- doc
- user
- application_security... |
https://docs.gitlab.com/user/application_security/dast/browser/798.42 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.42.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.42.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 API token | null |
## Description
The response body contains content that matches the pattern of a Finicity 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 ... | ---
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 API token
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/798.130 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.130.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.130.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 Anthropic API key | null |
## Description
The response body contains content that matches the pattern of an Anthropic API key was detected. Anthropic keys are used to access generative AI services. Malicious actors could use these keys to build up excessive charges to your account.
Exposing this value could allow attackers to gain access to a... | ---
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 Anthropic API key
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.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 confidential secret or token Adobe Client ID (OAuth Web) | null |
## Description
The response body contains content that matches the pattern of a Adobe Client ID (OAuth Web).
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 th... | ---
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 Adobe Client ID (OAuth Web)
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.136 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.136.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.136.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 personal access token | null |
## Description
The response body contains content that matches the pattern of a DigitalOcean Personal 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... | ---
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 personal access... |
https://docs.gitlab.com/user/application_security/dast/browser/798.4 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.4.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.4.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 Age secret key | null |
## Description
The response body contains content that matches the pattern of an age encryption secret key was detected. Age is a modern and secure file encryption tool, format, and Go library. It features small explicit keys, no configuration options, and UNIX-style composability. These keys are usually used for en... | ---
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 Age secret key
breadcrumbs:
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.106 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.106.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.106.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 custom app access token | null |
## Description
The response body contains content that matches the pattern of a Shopify custom app 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 se... | ---
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 custom app access to... |
https://docs.gitlab.com/user/application_security/dast/browser/798.74 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.74.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.74.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 Mailgun private API token | null |
## Description
The response body contains content that matches the pattern of a Mailgun private API token was identified. This key allows you to perform read, write, and delete operations through various API endpoints and for any of your sending domains. A malicious actor with access to this key can perform any API ... | ---
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 Mailgun private API token
br... |
https://docs.gitlab.com/user/application_security/dast/browser/798.93 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.93.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.93.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 Postman API token | null |
## Description
The response body contains content that matches the pattern of a Postman API token was identified. An API key provides access to any Postman data the account has permissions to. A malicious actor with access to this token can access all data stored in the Postman service that the user who created the ... | ---
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 Postman API token
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/598.3 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/598.3.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 598.3.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 (Authorization header details) | null |
## Description
The authorization header value was identified in the request URL. These headers typically contain
usernames and passwords or JWT tokens. These values should never 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 ... | ---
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 (Authorization... |
https://docs.gitlab.com/user/application_security/dast/browser/798.72 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.72.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.72.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 Mailchimp API key | null |
## Description
The response body contains content that matches the pattern of a Mailchimp API key was identified. API keys can be used send emails, create and send marketing campaigns, access customer lists and email addresses. A malicious actor with access to this key can perform any API request to Mailchimp withou... | ---
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 Mailchimp API key
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.95 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.95.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.95.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 Pulumi API token | null |
## Description
The response body contains content that matches the pattern of a Pulumi API token was identified. Personal access tokens map to the permissions of a user. A malicious actor with access to this token can delete stacks, tags, updates, and webhooks as the owner of the access token. Exposing this value co... | ---
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 Pulumi API token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.110 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.110.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.110.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 webhook | null |
## Description
The response body contains content that matches the pattern of a Slack webhook URL was detected. Slack webhook URLs are used to post messages from external sources into Slack. They make use of HTTP requests with a JSON payload, which includes the message and a few other optional details. You can inclu... | ---
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 webhook
breadcrumbs:
-... |
https://docs.gitlab.com/user/application_security/dast/browser/16.9 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.9.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.9.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-Report-Only analysis | null |
## Description
A `Content-Security-Policy-Report-Only` (CSPRO) was identified on the target site. CSP-Report-Only headers
aid in determining how to implement a `Content-Security-Policy` that does not disrupt normal use of the target
site.
## Remediation
Follow the recommendations to determine if any actions are ne... | ---
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-Report-Only analysis
breadcrumbs:
- doc
- use... |
https://docs.gitlab.com/user/application_security/dast/browser/798.83 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.83.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.83.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 ingest browser API token | null |
## Description
The response body contains content that matches the pattern of a New Relic ingest browser API token 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 lea... | ---
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 ingest browser API... |
https://docs.gitlab.com/user/application_security/dast/browser/829.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/829.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 829.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 | Invalid Sub-Resource Integrity values detected | null |
## Description
JavaScript or CSS source files were found to contain invalid
[Sub-Resource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity)
`integrity` values or a missing `crossorigin` value. These scripts or links should be investigated to
ensure they have not been malic... | ---
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: Invalid Sub-Resource Integrity values detected
breadcrumbs:
- doc
- u... |
https://docs.gitlab.com/user/application_security/dast/browser/798.171 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.171.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.171.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 Test API token | null |
## Description
The response body contains content that matches the pattern of a Shippo Test 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.
Exp... | ---
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 Test API token
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.177 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.177.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.177.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 secret test key | null |
## Description
The response body contains content that matches the pattern of a Stripe secret test key was identified. Test secret keys are used for accessing and executing test data and functionality. A malicious actor with access to this test key can only simulate access, account objects do not return sensitive fi... | ---
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 secret test key
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/798.79 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.79.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.79.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 MessageBird API client ID | null |
## Description
The response body contains content that matches the pattern of a MessageBird API client 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 ... | ---
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 MessageBird API client ID
br... |
https://docs.gitlab.com/user/application_security/dast/browser/16.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.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 | Server header exposes version information | null |
## Description
The target website returns the `Server` header and 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
vulnerab... | ---
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 header exposes version information
breadcrumbs:
- doc
- user
-... |
https://docs.gitlab.com/user/application_security/dast/browser/79.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/79.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 79.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 | Cross Site Scripting | null |
## Description
Cross Site Scripting (XSS) is an attack which exploits a web application or system to treat user input
as markup or script code. It is important to encode the data depending on the specific context it
is used in. There are at least six context types:
- Inside HTML tags `<div>context 1</div>`
- Inside... | ---
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: Cross Site Scripting
breadcrumbs:
- doc
- user
- application_security... |
https://docs.gitlab.com/user/application_security/dast/browser/798.161 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.161.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.161.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 Meta access token | null |
## Description
The response body contains content that matches the pattern of a Meta 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 d... | ---
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 Meta access token
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/16.4 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.4.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.4.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 | X-Backend-Server header exposes server information | null |
## Description
The target website returns the `X-Backend-Server` header which includes potentially internal/hidden IP addresses
or hostnames. By exposing these values, attackers may attempt to circumvent security proxies and access these
hosts directly.
## Remediation
Consult your proxy/load balancer documentation... | ---
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: X-Backend-Server header exposes server information
breadcrumbs:
- doc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.167 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.167.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.167.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 PKCS8 private key | null |
## Description
The response body contains content that matches the pattern of a PKCS8 private key was identified. PKCS #8 is a standard syntax for storing private key information. A malicious actor with access to this key can encrypt and decrypt all past and future messages. Note that past messages encrypted using t... | ---
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 PKCS8 private key
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.180 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.180.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.180.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 Tailscale key | null |
## Description
The response body contains content that matches the pattern of Tailscale keys.
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 docume... | ---
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 Tailscale key
breadcrumbs:
-... |
https://docs.gitlab.com/user/application_security/dast/browser/798.69 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.69.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.69.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 LinkedIn client secret | null |
## Description
The response body contains content that matches the pattern of a LinkedIn client secret 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 users' information.
Exposing ... | ---
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 LinkedIn client secret
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/798.13 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.13.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.13.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 Bitbucket client ID | null |
## Description
The response body contains content that matches the pattern of a Bitbucket client 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... | ---
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 Bitbucket client ID
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.59 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.59.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.59.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 Heroku API key or application authorization token | null |
## Description
The response body contains content that matches the pattern of a Heroku API key or application authorization token was identified. API keys and authorization tokens can be used to perform API calls on behalf of a user or account. A malicious actor with access to these tokens can access the Heroku API ... | ---
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 Heroku API key or applicatio... |
https://docs.gitlab.com/user/application_security/dast/browser/798.23 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.23.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.23.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 delivery API token | null |
## Description
The response body contains content that matches the pattern of a Contentful delivery API token was identified. The Contentful Delivery API (CDA) is a read-only API for delivering content from Contentful to apps, websites and other media. Content is delivered as JSON data, and images, videos and other ... | ---
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 delivery API toke... |
https://docs.gitlab.com/user/application_security/dast/browser/798.151 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.151.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.151.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 SCIM OAuth token | null |
## Description
The response body contains content that matches the pattern of a GitLab SCIM token was identified. The SCIM token is used to configure third party Identity providers (IdP). A malicious actor with access to this token can configure an IdP and add users to gain access to the GitLab system..
Exposing thi... | ---
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 SCIM OAuth token
brea... |
https://docs.gitlab.com/user/application_security/dast/browser/287.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/287.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 287.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 | Insecure authentication over HTTP (Digest Authentication) | null |
## Description
The target application was found to authenticate users using the Digest Authentication scheme over HTTP.
Digest Authentication uses an insecure hashing algorithm (MD5) to hash the username and password and sends
it in the `Authentication` header. Attackers who are in between the communication path (or... | ---
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 (Digest Authentication)
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.157 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.157.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.157.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 Ionic personal access token | null |
## Description
The response body contains content that matches the pattern of an Ionic personal access token was identified. Personal access tokens can be used to authenticate the Ionic CLI, Appflow CLI, or any third party application. A malicious actor with access to this token can gain full access to linked reposi... | ---
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 Ionic personal access token
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.35 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.35.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.35.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 Dynatrace API token | null |
## Description
The response body contains content that matches the pattern of a Dynatrace 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... | ---
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 Dynatrace API token
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/943.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/943.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 943.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 special elements in data query logic | null |
## Description
The application generates a query intended to interact with MongoDB,
but it does not neutralize or incorrectly neutralizes special elements
that can modify the intended logic of the query.
## Remediation
Refactor find or search queries to use standard
filtering operators such as `$gt` or `$in` inste... | ---
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 special elements in data query logic
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/798.141 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.141.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.141.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 (routable) | null |
## Description
The response body contains content that matches the pattern of a GitLab Personal Access Token (routable).
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, p... | ---
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... |
https://docs.gitlab.com/user/application_security/dast/browser/798.147 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.147.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.147.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 feed token v2 | null |
## Description
The response body contains content that matches the pattern of a GitLab feed token was identified. Your feed token authenticates you when your RSS reader loads a personalized RSS feed or when your calendar application loads a personalized calendar. It is visible in those feed URLs. It cannot be used t... | ---
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 feed token v2
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/798.9 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.9.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.9.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 ID | null |
## Description
The response body contains content that matches the pattern of an Asana Client ID was detected. This ID is used in conjunction with the client secret. A malicious actor with access to this ID can impersonate the client application if they also have access to the client secret..
Exposing this value cou... | ---
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 ID
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/614.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/614.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 614.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 Secure attribute | null |
## Description
The cookie was transmitted in a `Set-Cookie` response without the `Secure` attribute set.
To prevent sensitive cookie values being accidentally transmitted over clear-text HTTP we
recommended that cookies are declared with the `Secure` attribute.
## Remediation
Most web application frameworks allow ... | ---
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 Secure attribute
breadcrumbs:
- doc
- user
-... |
https://docs.gitlab.com/user/application_security/dast/browser/798.39 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.39.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.39.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 Facebook token | null |
## Description
The response body contains content that matches the pattern of a Facebook 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 docu... | ---
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 Facebook token
breadcrumbs:
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.137 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.137.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.137.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 refresh token | null |
## Description
The response body contains content that matches the pattern of a DigitalOcean OAuth Refresh 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 s... | ---
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 refresh token
b... |
https://docs.gitlab.com/user/application_security/dast/browser/798.131 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.131.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.131.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 access token | null |
## Description
The response body contains content that matches the pattern of a CircleCI project token was identified. CircleCI project tokens can be given one of three scopes: - Status - Read Only - Admin Depending on the access level of this detected token, a malicious actor with access to this token may be able t... | ---
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 access token
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.3 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.3.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.3.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 Adobe client secret | null |
## Description
The response body contains content that matches the pattern of an Adobe client secret was detected. Adobe client secrets are used to connect to various API or webhook event based services. Depending on which type of service was defined for a project, a malicious actor with access to the secret can use... | ---
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 Adobe client secret
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.53 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.53.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.53.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 GitHub OAuth Access Token | null |
## Description
The response body contains content that matches the pattern of a GitHub OAuth Access Token was identified. Unlike a traditional OAuth token, user access tokens do not use scopes. Instead, it uses fine-grained permissions. A user access token only has permissions that both the user and the app have. If... | ---
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 GitHub OAuth Access Token
br... |
https://docs.gitlab.com/user/application_security/dast/browser/798.29 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.29.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.29.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 Doppler API token | null |
## Description
The response body contains content that matches the pattern of a Doppler personal access token was detected.
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... | ---
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 Doppler API token
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.55 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.55.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.55.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 GitHub refresh token | null |
## Description
The response body contains content that matches the pattern of a GitHub Refresh 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 GitLa... | ---
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 GitHub refresh token
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/94.3 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/94.3.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 94.3.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 (Python) | null |
## Description
The target application was found vulnerable to code injection. A malicious actor could inject arbitrary
Python 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
Ne... | ---
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 (Python)
breadcrumbs:
- doc
- user
- appli... |
https://docs.gitlab.com/user/application_security/dast/browser/319.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/319.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 319.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 | Mixed Content | null |
## Description
The target application was found to request resources over insecure transport protocols (HTTP). This is usually due to HTML
elements which load resources using the `http://` scheme instead of `https://`. It should be noted that most modern browsers
block these requests automatically so there is limite... | ---
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: Mixed Content
breadcrumbs:
- doc
- user
- application_security
- dast... |
https://docs.gitlab.com/user/application_security/dast/browser/798.121 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.121.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.121.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 X token | null |
## Description
The response body contains content that matches the pattern of an X secret access token was identified. An access secret are user-specific credentials used to authenticate OAuth 1.0a API requests. They specify the X account the request is made on behalf of. A malicious actor with access to this token ... | ---
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 X token
breadcrumbs:
- doc
-... |
https://docs.gitlab.com/user/application_security/dast/browser/16.8 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.8.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.8.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 analysis | null |
## Description
A missing or invalid `Content-Security-Policy` (CSP) was identified on the target site. CSP can aid in
hardening a website against various client side attacks such as Cross-Site Scripting (XSS).
## Remediation
If the target site is missing a CSP, investigate the relevant URLs for enabling CSP. Other... | ---
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 analysis
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/dast/browser/798.117 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.117.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.117.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 Twilio API key | null |
## Description
The response body contains content that matches the pattern of a Twilio 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 docu... | ---
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 Twilio API key
breadcrumbs:
... |
https://docs.gitlab.com/user/application_security/dast/browser/359.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/359.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 359.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 Private Personal Information (PII) to an unauthorized actor (credit card) | null |
## Description
The target application was found to return credit card information in the response. Organizations
found returning such information may be in violation of industry regulations and could face fines.
## Remediation
PII such as credit cards should never be directly returned to the user. The majority of ... | ---
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 act... |
https://docs.gitlab.com/user/application_security/dast/browser/798.111 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.111.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.111.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 secret key | null |
## Description
The response body contains content that matches the pattern of a Stripe live secret key was identified. Live secret keys authenticate requests on your server when in live mode. By default, you can use this key to perform any API request without restriction. A malicious actor who gained access to this ... | ---
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 secret key
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/798.84 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.84.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.84.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 npm access token | null |
## Description
The response body contains content that matches the pattern of an npm access token was identified. Access tokens can either be classic or granular, both of which allow customization of permissions. Depending on the permissions, a malicious actor with access to this token can read packages and package ... | ---
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 npm access token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/200.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/200.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 200.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 sensitive information to an unauthorized actor (private IP address) | null |
## Description
A private RFC 1918/RFC 4193 address was identified in the target application. Public facing websites should not be issuing
requests to private IP Addresses. Attackers attempting to execute subsequent attacks, such as Server-Side
Request Forgery (SSRF), may be able to use this information to identify a... | ---
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 sensitive information to an unauthorized actor (private I... |
https://docs.gitlab.com/user/application_security/dast/browser/798.82 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.82.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.82.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 ID | null |
## Description
The response body contains content that matches the pattern of a New Relic user API 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 GitL... | ---
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 ID
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.107 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.107.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.107.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 private app access token | null |
## Description
The response body contains content that matches the pattern of a Shopify private app 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 s... | ---
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 private app access t... |
https://docs.gitlab.com/user/application_security/dast/browser/798.101 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.101.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.101.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 SendGrid API token | null |
## Description
The response body contains content that matches the pattern of a SendGrid 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 ... | ---
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 SendGrid API token
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/598.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/598.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 598.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 | Use of GET request method with sensitive query strings (password) | null |
## Description
The user's password was identified in the request URL. Passwords should never 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 these logs or logging systems, they would
be able to gain access to the... | ---
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 (password)
bre... |
https://docs.gitlab.com/user/application_security/dast/browser/798.73 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.73.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.73.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 Mailgun public verification key | null |
## Description
The response body contains content that matches the pattern of a Mailgun public verification key was identified. These keys are deprecated and you should use the v4 verification service instead. A malicious with access to this key can use it to validate email addresses.
Exposing this value could allow... | ---
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 Mailgun public verification ... |
https://docs.gitlab.com/user/application_security/dast/browser/798.94 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.94.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.94.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 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 att... | ---
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 private key
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.75 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.75.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.75.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 Mailgun webhook signing key | null |
## Description
The response body contains content that matches the pattern of a Mailgun webhook signing key was identified. This key is used by Mailgun to sign all incoming webhook message payloads. A malicious actor with access to this key can potentially sign fake webhook events and send it to your service to pass... | ---
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 Mailgun webhook signing key
... |
https://docs.gitlab.com/user/application_security/dast/browser/authentication | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/authentication.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | authentication.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 | Authentication | null |
For complete coverage, the DAST analyzer must authenticate with the application being tested. This
requires configuring the authentication credentials and authentication method in the DAST CI/CD job.
DAST requires authentication to:
- Simulate real-world attacks and identify vulnerabilities that might be exploited ... | ---
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: Authentication
breadcrumbs:
- doc
- user
- app... |
https://docs.gitlab.com/user/application_security/dast/browser/overriding_analyzer_jobs | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/overriding_analyzer_jobs.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | overriding_analyzer_jobs.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 | Overriding DAST jobs | null |
To override a job definition, (for example, change properties like `variables`, `dependencies`, or [`rules`](../../../../../ci/yaml/_index.md#rules)),
declare a job with the same name as the DAST job to override. Place this new job after the template
inclusion and specify any additional keys under it. For example, th... | ---
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: Overriding DAST jobs
breadcrumbs:
- doc
- user... |
https://docs.gitlab.com/user/application_security/dast/browser/offline_configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/offline_configuration.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | offline_configuration.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 | Offline configuration | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
For instances in an environment with limited, restricted, or intermittent access
to external resources through the internet, some adjustments are required for the DAST job to
successfully run. For more information, see [Offline envir... | ---
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: Offline configuration
breadcrumbs:
- doc
- use... |
https://docs.gitlab.com/user/application_security/dast/browser/requirements | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/requirements.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | requirements.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../application_deployment_options.md).
<!-- This redirect file can be deleted after <2025-09-17>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different p... | ---
redirect_to: ../application_deployment_options.md
remove_date: '2025-09-17'
breadcrumbs:
- doc
- user
- application_security
- dast
- browser
- configuration
---
<!-- markdownlint-disable -->
This document was moved to [another location](../application_deployment_options.md).
<!-- This redirect file can be dele... |
https://docs.gitlab.com/user/application_security/dast/browser/enabling_the_analyzer | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/enabling_the_analyzer.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | enabling_the_analyzer.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 | Enabling the analyzer | null |
To run a DAST scan:
- Read the [requirements](../_index.md) conditions for running a DAST scan.
- Create a [DAST job](#create-a-dast-cicd-job) in your CI/CD pipeline.
- [Authenticate](authentication.md) as a user if your application requires it.
The DAST job runs in a Docker container defined by the `image` keyword... | ---
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: Enabling the analyzer
breadcrumbs:
- doc
- use... |
https://docs.gitlab.com/user/application_security/dast/browser/customize_settings | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/customize_settings.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | customize_settings.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 | Customize analyzer settings | null |
## Managing scope
Scope controls what URLs DAST follows when crawling the target application. Properly managed scope minimizes scan run time while ensuring only the target application is checked for vulnerabilities.
### Types of scope
There are three types of scope:
- in scope
- out of scope
- excluded from scope... | ---
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: Customize analyzer settings
breadcrumbs:
- doc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.