url stringlengths 24 122 | repo_url stringlengths 60 156 | date_extracted stringdate 2025-08-13 00:00:00 2025-08-13 00:00:00 | root stringlengths 3 85 | breadcrumbs listlengths 1 6 | filename stringlengths 6 60 | stage stringclasses 33
values | group stringclasses 81
values | info stringclasses 22
values | title stringlengths 3 110 ⌀ | description stringlengths 11 359 ⌀ | clean_text stringlengths 47 3.32M | rich_text stringlengths 321 3.32M |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://docs.gitlab.com/user/application_security | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/_index.md | 2025-08-13 | doc/user/application_security | [
"doc",
"user",
"application_security"
] | _index.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Application security testing | Scanning, vulnerabilities, compliance, customization, and reporting. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Build security into your development process with GitLab application security testing capabilities.
These features help you identify and address vulnerabilities early in your development l... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Application security testing
description: Scanning, vulnerabilities, c... |
https://docs.gitlab.com/user/secure_your_application | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/secure_your_application.md | 2025-08-13 | doc/user/application_security | [
"doc",
"user",
"application_security"
] | secure_your_application.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Secure your application | Container, dependency, and vulnerability scans. |
GitLab can check your applications for security vulnerabilities.
{{< cards >}}
- [Getting started](get-started-security.md)
- [Tutorials](../../tutorials/secure_application.md)
- [Application security](_index.md)
- [Compliance](../compliance/_index.md)
- [Detect](detect/_index.md)
- [Triage](triage/_index.md)
- [An... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Container, dependency, and vulnerability scans.
title: Secure yo... |
https://docs.gitlab.com/user/cve_id_request | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/cve_id_request.md | 2025-08-13 | doc/user/application_security | [
"doc",
"user",
"application_security"
] | cve_id_request.md | Security Risk Management | Security Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | CVE ID request | Vulnerability tracking and security disclosure. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com
{{< /details >}}
For any public project, you can request a CVE identifier (ID).
A [CVE](https://cve.mitre.org/index.html) identifier is assigned to a publicly-disclosed software
vulnerability. GitLab is a [CVE Numbering Authority](https://abou... | ---
stage: Security Risk Management
group: Security Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: CVE ID request
description: Vulnerability tracking and security disclosu... |
https://docs.gitlab.com/user/troubleshooting_application_security | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/troubleshooting_application_security.md | 2025-08-13 | doc/user/application_security | [
"doc",
"user",
"application_security"
] | troubleshooting_application_security.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting application security | How to troubleshoot GitLab application security features, including how to get more detailed logging. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
When working with application security features, you might encounter the following issues.
## Logging level
The verbosity of logs output by GitLab analyzers is determined by the `SECURE_LOG_LEVEL` envi... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting application security
description: How to troubleshoot ... |
https://docs.gitlab.com/user/application_security/on-demand_scan | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/on-demand_scan.md | 2025-08-13 | doc/user/application_security/dast | [
"doc",
"user",
"application_security",
"dast"
] | on-demand_scan.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | DAST on-demand scan | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
Do not run DAST scans against a production server. Not only can it perform any function that a user can, such
as clicking buttons or submitting forms, but it may also trigge... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: DAST on-demand scan
breadcrumbs:
- doc
- user
- application_security
... |
https://docs.gitlab.com/user/application_security/dast | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/dast | [
"doc",
"user",
"application_security",
"dast"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Dynamic Application Security Testing (DAST) | Automated penetration testing, vulnerability detection, web application scanning, security assessment, and CI/CD integration. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
The DAST proxy-based analyzer was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966)
in GitLab 16.9 and [removed](https://gitlab.com/groups/gitlab-org/-/epic... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Dynamic Application Security Testing (DAST)
description: Automated pe... |
https://docs.gitlab.com/user/application_security/browser_based_4_to_5_migration_guide | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/browser_based_4_to_5_migration_guide.md | 2025-08-13 | doc/user/application_security/dast | [
"doc",
"user",
"application_security",
"dast"
] | browser_based_4_to_5_migration_guide.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Migrating from the DAST version 4 browser-based analyzer to DAST version 5 | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The [DAST proxy-based analyzer](proxy_based_to_browser_based_migration_guide.md) was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966) in GitLab 16.6 and removed in 17... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Migrating from the DAST version 4 browser-based analyzer to DAST vers... |
https://docs.gitlab.com/user/application_security/profiles | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/profiles.md | 2025-08-13 | doc/user/application_security/dast | [
"doc",
"user",
"application_security",
"dast"
] | profiles.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | DAST profiles | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
DAST site and scanner profiles save information related to your applications and the scanners you use to evaluate them.
Once you define a profile, you can use it for pipeline and on-demand DAST jobs.
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: DAST profiles
breadcrumbs:
- doc
- user
- application_security
- dast... |
https://docs.gitlab.com/user/application_security/proxy_based_to_browser_based_migration_guide | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/proxy_based_to_browser_based_migration_guide.md | 2025-08-13 | doc/user/application_security/dast | [
"doc",
"user",
"application_security",
"dast"
] | proxy_based_to_browser_based_migration_guide.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Migrating from the DAST proxy-based analyzer to DAST version 5 | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The [DAST proxy-based analyzer](proxy_based_to_browser_based_migration_guide.md) was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/430966) in GitLab 16.6 and removed in 17... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Migrating from the DAST proxy-based analyzer to DAST version 5
breadc... |
https://docs.gitlab.com/user/application_security/dast/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/troubleshooting.md | 2025-08-13 | doc/user/application_security/dast/browser | [
"doc",
"user",
"application_security",
"dast",
"browser"
] | troubleshooting.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting DAST scans | null |
The following troubleshooting scenarios have been collected from customer support cases. If you
experience a problem not addressed here, or the information here does not fix your problem, create a
support ticket. For more details, see the [GitLab Support](https://about.gitlab.com/support/) page.
## When something go... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting DAST scans
breadcrumbs:
- doc
... |
https://docs.gitlab.com/user/application_security/dast/application_deployment_options | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/application_deployment_options.md | 2025-08-13 | doc/user/application_security/dast/browser | [
"doc",
"user",
"application_security",
"dast",
"browser"
] | application_deployment_options.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Application deployment options | null |
DAST requires a deployed application to be available to scan.
Depending on the complexity of the target application, there are a few options as to how to deploy and configure
the DAST template. A set of example applications have been provided with their configurations in the
[DAST demonstrations](https://gitlab.com/... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Application deployment options
breadcrumbs:
- ... |
https://docs.gitlab.com/user/application_security/dast/browser | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/_index.md | 2025-08-13 | doc/user/application_security/dast/browser | [
"doc",
"user",
"application_security",
"dast",
"browser"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | DAST browser-based analyzer | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Generally available](https://gitlab.com/groups/gitlab-org/-/epics/9023) in GitLab 15.7 (GitLab DAST v3.0.50).
{{< /history >}}
{{< alert type="warning" >}}
The DAST version 4 brows... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: DAST browser-based analyzer
breadcrumbs:
- doc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.56 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.56.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.56.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GitLab personal access token | null |
## Description
The response body contains content that matches the pattern of a GitLab personal access token was identified. Personal access tokens can be used to access GitLab services as the user who created them. In most cases these tokens are given read-write access to all repositories. A malicious actor with ac... | ---
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.50 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.50.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.50.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GoCardless API token | null |
## Description
The response body contains content that matches the pattern of a GoCardless API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 GoCardless API token
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/798.124 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.124.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.124.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Typeform personal access token | null |
## Description
The response body contains content that matches the pattern of a Typeform personal access token was identified. Personal access tokens are for accessing the Typeform API. depending on the assigned scope and permissions, a malicious actor with access to this token can read, update, or delete form data.... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Typeform personal access tok... |
https://docs.gitlab.com/user/application_security/dast/browser/798.158 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.158.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.158.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Artifactory API Key | null |
## Description
The response body contains content that matches the pattern of an Artifactory API Key was identified. An Artifactory API Key enable actions like deploying artifacts, managing repositories, configuring permissions, and retrieving artifacts from JFrog Artifactory repositories. If leaked, a malicious 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 Artifactory API Key
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.46 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.46.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.46.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Flutterwave test secret key | null |
## Description
The response body contains content that matches the pattern of a test Flutterwave secret key was identified. Secret keys have the highest level of privileges and can authorize any action on your account. However, this is a test key so it can only be used for fake transactions. A malicious actor with 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 Flutterwave test secret key
... |
https://docs.gitlab.com/user/application_security/dast/browser/601.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/601.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 601.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | URL redirection to untrusted site (open redirect) | null |
## Description
This site was found to allow open redirects from user supplied input. Open redirects are commonly
abused in phishing attacks where the original domain or URL looks like a legitimate link, but then
redirects a user to a malicious site. An example would be
`https://example.com/redirect?url=https://%62%6... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: URL redirection to untrusted site (open redirect)
breadcrumbs:
- doc
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.40 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.40.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.40.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Fastly API user or automation token | null |
## Description
The response body contains content that matches the pattern of a Fastly API user or automation token was identified. Fastly API tokens can grant read write or read only access depending on how they are configured.
Exposing this value could allow attackers to gain access to all resources granted by 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 Fastly API user or automatio... |
https://docs.gitlab.com/user/application_security/dast/browser/16.10 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.10.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.10.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Content-Security-Policy violations | null |
## Description
A `Content-Security-Policy` (CSP) was identified on the target site that is reporting violations when
attempting to load the page in a browser. This may cause disruption to your users when attempting to visit the page.
## Remediation
Review the violations to determine if any action is necessary.
##... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Content-Security-Policy violations
breadcrumbs:
- doc
- user
- applic... |
https://docs.gitlab.com/user/application_security/dast/browser/798.132 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.132.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.132.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token CircleCI Personal Access Token | null |
## Description
The response body contains content that matches the pattern of a CircleCI personal access token was identified. Personal access tokens grant the same level of permissions as the user that created the token. A malicious actor with access to this token can impersonate the user and gain access to all fea... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token CircleCI Personal Access Tok... |
https://docs.gitlab.com/user/application_security/dast/browser/798.134 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.134.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.134.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Contentful personal access token | null |
## Description
The response body contains content that matches the pattern of a Contentful personal access token was identified. Personal access tokens are tied to the user who requests them and carry the same permissions, including access to organizations, spaces, and content.
Exposing this value could allow attack... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Contentful personal access t... |
https://docs.gitlab.com/user/application_security/dast/browser/798.148 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.148.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.148.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GitLab Kubernetes agent token | null |
## Description
The response body contains content that matches the pattern of a GitLab Agent for Kubernetes token was identified. The Kubernetes access token is used to authenticate the GitLab agent for Kubernetes with a Kubernetes cluster. A malicious actor with access to this token can access source code in the ag... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token GitLab Kubernetes agent toke... |
https://docs.gitlab.com/user/application_security/dast/browser/798.102 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.102.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.102.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Brevo API token | null |
## Description
The response body contains content that matches the pattern of a Brevo API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab doc... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Brevo API token
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.104 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.104.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.104.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Shippo API token | null |
## Description
The response body contains content that matches the pattern of a live Shippo API token was identified. API tokens can be used to access the Shippo API which is used for shipping services. A malicious actor with access to this token can access billing and order information and modify shipping data.
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 API token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.178 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.178.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.178.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Stripe restricted test key | null |
## Description
The response body contains content that matches the pattern of a Stripe restricted test key was identified. Test restricted keys offer greater security by only allowing read or write access to specific API resources. A malicious actor with access to this key is limited by the scope defined and can onl... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Stripe restricted test key
b... |
https://docs.gitlab.com/user/application_security/dast/browser/548.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/548.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 548.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of information through directory listing | null |
## Description
The target web server is configured to list the contents of directories that do not contain an index file
such as `index.html`. This could lead to accidental exposure of sensitive information, or give an attacker
details on how filenames and directories are structured and stored.
## Remediation
Dire... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of information through directory listing
breadcrumbs:
- doc
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.91 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.91.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.91.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token PlanetScale API token | null |
## Description
The response body contains content that matches the pattern of a PlanetScale API service token was identified. Service tokens are created and assigned permissions depending on the allowed scope. A malicious actor with access to the service token is granted the same permissions that were assigned to 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 PlanetScale API token
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/598.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/598.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 598.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Use of GET request method with sensitive query strings (session ID) | null |
## Description
A session ID was identified in the request URL as well as a cookie value. Session
IDs should not be sent in GET requests as they maybe captured by proxy systems, stored in
browser history, or stored in log files. If an attacker were to get access to the session
ID they would potentially be able to gai... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Use of GET request method with sensitive query strings (session ID)
b... |
https://docs.gitlab.com/user/application_security/dast/browser/798.70 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.70.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.70.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Lob API key | null |
## Description
The response body contains content that matches the pattern of a Lob API key was identified. API keys can be used to verify addresses, create campaigns, print, or mail directly to customers. A malicious actor with access to this key can perform any API request to Lob without restriction.
Exposing this... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Lob API key
breadcrumbs:
- d... |
https://docs.gitlab.com/user/application_security/dast/browser/798.97 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.97.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.97.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token RubyGems API token | null |
## Description
The response body contains content that matches the pattern of a RubyGems API token was identified. RubyGems tokens are used for accessing the API or publishing packages. RubyGems tokens can be created with specific permissions or scopes. Depending on the permissions and scope, a malicious actor with ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token RubyGems API token
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/359.2 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/359.2.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 359.2.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of Private Personal Information (PII) to an unauthorized actor (United States social security number) | null |
## Description
The target application was found to return Social Security Number (SSN) information in the response. Organizations
found returning such information may be in violation of (United States) state or federal laws and may face stiff penalties.
## Remediation
PII such as social security numbers should nev... | ---
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.168 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.168.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.168.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token RSA private key | null |
## Description
The response body contains content that matches the pattern of an RSA private key was identified. Private RSA keys can be used in many types of applications but generally are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an appl... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token RSA private key
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.66 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.66.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.66.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Linear API token | null |
## Description
The response body contains content that matches the pattern of a Linear API token was identified. Personal API tokens can be used to access Linear's GraphQL API. A malicious actor with access to this token can read or write issues, projects and teams to Linear and any systems the account has been inte... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Linear API token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.81 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.81.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.81.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token New Relic user API key | null |
## Description
The response body contains content that matches the pattern of a New Relic user API key was identified. User keys are used for querying data and managing configurations (Alerts, Synthetics, dashboards, etc.). A malicious actor with access to this key can execute API requests as the user who created it... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token New Relic user API key
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/798.60 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.60.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.60.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token HubSpot private app API token | null |
## Description
The response body contains content that matches the pattern of a HubSpot private app API token was identified. Private apps allow you to use HubSpot's APIs to access specific data from your HubSpot account and can be restricted by setting specific scopes. A malicious actor with access to this token ca... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token HubSpot private app API toke... |
https://docs.gitlab.com/user/application_security/dast/browser/16.7 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.7.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.7.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Strict-Transport-Security header missing or invalid | null |
## Description
The `Strict-Transport-Security` header was found to be missing or invalid. The `Strict-Transport-Security`
header allows web site operators to force communications to occur over a TLS connection. By enabling this
header, websites can protect their users from various forms of network eavesdropping or i... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Strict-Transport-Security header missing or invalid
breadcrumbs:
- do... |
https://docs.gitlab.com/user/application_security/dast/browser/798.118 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.118.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.118.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Twitch OAuth client secret | null |
## Description
The response body contains content that matches the pattern of a Twitch OAuth client secret was identified. OAuth client secrets are used to allow the service to execute functionality on behalf of Twitch users. A malicious actor with access to this client secret can impersonate the service and execute... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Twitch OAuth client secret
b... |
https://docs.gitlab.com/user/application_security/dast/browser/798.164 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.164.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.164.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token OpenAI API key | null |
## Description
The response body contains content that matches the pattern of a OpenAI API key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab 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 OpenAI API key
breadcrumbs:
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.183 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.183.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.183.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-3 | null |
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM API key v1.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Yandex Cloud IAM cookie v1-3... |
https://docs.gitlab.com/user/application_security/dast/browser/16.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Missing Content-Type header | null |
## Description
The `Content-Type` header ensures that user agents correctly interpret the data being received. Without this header
being sent, the browser may misinterpret the data, leading to MIME confusion attacks. If an attacker were able
to upload files that are accessible by using a browser, they could upload f... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Missing Content-Type header
breadcrumbs:
- doc
- user
- application_s... |
https://docs.gitlab.com/user/application_security/dast/browser/798.162 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.162.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.162.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Oculus access token | null |
## Description
The response body contains content that matches the pattern of an Oculus access token was identified. User tokens are needed any time your app calls an API to read, modify or write a specific person's Oculus data on their behalf. A malicious actor with access to this token can call the Oculus API on b... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Oculus access token
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.10 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.10.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.10.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Asana client secret | null |
## Description
The response body contains content that matches the pattern of an Asana Client Secret was detected. Client Secrets are used for authentication and authorization using OAuth. A malicious actor who got access to this secret could gain access to user accounts and execute functionality on their behalf.
Ex... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Asana client secret
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/918.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/918.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 918.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Server-Side Request Forgery | null |
## Description
The application is susceptible to Server-Side Request Forgery (SSRF), a high-risk vulnerability
that allows attackers to make unauthorized requests to internal and external resources. This
vulnerability arises when user-controlled input is not properly validated or sanitized before
being used in reque... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Server-Side Request Forgery
breadcrumbs:
- doc
- user
- application_s... |
https://docs.gitlab.com/user/application_security/dast/browser/checks | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/_index.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | DAST browser-based crawler vulnerability checks | null |
<!--
This file is autogenerated. Do not edit directly.
See: https://gitlab.com/gitlab-org/security-products/dast-cwe-checks/-/blob/main/doc/how-to-generate-the-markdown-documentation.md
-->
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
The [DAST br... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: DAST browser-based crawler vulnerability checks
breadcrumbs:
- doc
- ... |
https://docs.gitlab.com/user/application_security/dast/browser/693.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/693.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 693.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Missing X-Content-Type-Options: nosniff | null |
## Description
The `X-Content-Type-Options` header with the value `nosniff` ensures that user agents do not attempt to
guess the format of the data being received. User Agents such as browsers, commonly attempt to guess
what the resource type being requested is, through a process called MIME type sniffing.
Without ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Missing X-Content-Type-Options: nosniff'
breadcrumbs:
- doc
- user
-... |
https://docs.gitlab.com/user/application_security/dast/browser/798.108 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.108.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.108.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Shopify shared secret | null |
## Description
The response body contains content that matches the pattern of a Shopify shared secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Shopify shared secret
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.174 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.174.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.174.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token SSH (EC) private key | null |
## Description
The response body contains content that matches the pattern of an SSH private key was identified. Private SSH keys are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow atta... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token SSH (EC) private key
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/798.172 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.172.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.172.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Slack app level token | null |
## Description
The response body contains content that matches the pattern of a Slack app level token was identified. App level tokens are for use with Slack apps but only with specific APIs, which are related to the app across all organizations where the app is installed.
Three scope levels can be assigned:
- `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 Slack app level token
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.30 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.30.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.30.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Dropbox API secret/key | null |
## Description
The response body contains content that matches the pattern of a Dropbox API secret/key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Dropbox API secret/key
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/1336.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/1336.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 1336.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Server-Side Template Injection | null |
## Description
The application is vulnerable to Server-Side Template Injection (SSTI), which enables attackers to
manipulate templates on the server side. This vulnerability arises when untrusted user input is
directly used in server-side templates without adequate sanitization. Attackers can exploit this
weakness 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: Server-Side Template Injection
breadcrumbs:
- doc
- user
- applicatio... |
https://docs.gitlab.com/user/application_security/dast/browser/798.36 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.36.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.36.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token EasyPost production API key | null |
## Description
The response body contains content that matches the pattern of an EasyPost production API key was identified. Production API keys are used for live application operations and allow full account access. A malicious actor with access to this token can execute all API calls for the target environment.
Ex... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token EasyPost production API key
... |
https://docs.gitlab.com/user/application_security/dast/browser/22.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/22.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 22.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Improper limitation of a pathname to a restricted directory (Path traversal) | null |
## Description
The vulnerability can be exploited by inserting a payload into a
parameter on the URL endpoint which allows for reading arbitrary files.
This could be used to read sensitive files, access other users data, or aid in
exploitation to gain further system access.
## Remediation
User input should never b... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Improper limitation of a pathname to a restricted directory (Path tra... |
https://docs.gitlab.com/user/application_security/dast/browser/798.138 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.138.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.138.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GCP OAuth client secret | null |
## Description
The response body contains content that matches the pattern of a GCP OAuth client secret was identified. Client secret are used when allowing users to Sign in to your application. Depending on the scopes requested, a malicious actor with access to the secret can impersonate the service to access users... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token GCP OAuth client secret
brea... |
https://docs.gitlab.com/user/application_security/dast/browser/798.144 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.144.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.144.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GitLab runner authentication token | null |
## Description
The response body contains content that matches the pattern of a GitLab Runner authentication token was identified. These tokens allow users to register or authenticate as a runner with the selected project. A malicious actor with access to this token can add a custom runner to the pipeline and possib... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token GitLab runner authentication... |
https://docs.gitlab.com/user/application_security/dast/browser/798.142 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.142.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.142.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GitLab pipeline trigger token | null |
## Description
The response body contains content that matches the pattern of a GitLab pipeline trigger token was identified. Pipeline trigger tokens can be used to execute pipelines for a branch or tag of a project. The token impersonates a user's project access and permissions. A malicious actor with access to 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 pipeline trigger toke... |
https://docs.gitlab.com/user/application_security/dast/browser/798.20 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.20.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.20.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Clojars deploy token | null |
## Description
The response body contains content that matches the pattern of a Clojars deploy token was detected. A deploy token is used in place of a password when deploying, and cannot be used to sign in. Tokens can be scoped to:
- Any artifact you have access to ("*")
- Any artifact in a group you have access 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 Clojars deploy token
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/798.26 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.26.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.26.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Discord API key | null |
## Description
The response body contains content that matches the pattern of a Discord API key.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab doc... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Discord API key
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/287.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/287.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 287.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Insecure authentication over HTTP (Basic Authentication) | null |
## Description
The target application was found to authenticate users using the Basic Authentication scheme over HTTP.
Basic Authentication base64 encodes the username and password and sends it in the `Authentication` header.
Attackers who are in between the communication path (or on the same local network) of the c... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Insecure authentication over HTTP (Basic Authentication)
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.154 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.154.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.154.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token HashiCorp Vault batch token | null |
## Description
The response body contains content that matches the pattern of a HashiCorp Vault batch token was identified. Batch tokens are used when hundreds to thousands of systems need to access Vault but generating unique tokens would not scale. These tokens are usually short lived and bound to a specific vault... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token HashiCorp Vault batch token
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.152 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.152.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.152.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GitLab CI build token | null |
## Description
The response body contains content that matches the pattern of a GitLab CI build (job) token was identified. Job tokens are used to execute functionality in the context of a pipeline job. In most cases job tokens have limited privileges and can only be used to read from the repository where the pipeli... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token GitLab CI build token
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/611.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/611.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 611.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | External XML Entity Injection (XXE) | null |
## Description
It is possible to cause the application's XML parser to include external resources.
This can include files or in some circumstances initiate requests to third party
servers.
## Remediation
Consult the documentation for the XML Parser used by the target application for security
guidelines and hardeni... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: External XML Entity Injection (XXE)
breadcrumbs:
- doc
- user
- appli... |
https://docs.gitlab.com/user/application_security/dast/browser/798.41 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.41.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.41.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Finicity client secret | null |
## Description
The response body contains content that matches the pattern of a Finicity client secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Finicity client secret
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/917.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/917.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 917.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Expression Language Injection | null |
## Description
It is possible to execute arbitrary Expression Language (EL) statements on the target
application server. EL injection is a critical severity vulnerability that can lead to
full system compromise. EL injection can occur when attacker-controlled data is used to construct
EL statements without neutraliz... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Expression Language Injection
breadcrumbs:
- doc
- user
- application... |
https://docs.gitlab.com/user/application_security/dast/browser/1004.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/1004.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 1004.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Sensitive cookie without HttpOnly attribute | null |
## Description
The cookie was transmitted in a `Set-Cookie` header without the `HttpOnly` attribute set.
To prevent JavaScript being able to access the cookie value - usually via `document.cookies` - all
cookies that are used for authorization should have the `HttpOnly` attribute
set.
## Remediation
Most web appli... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Sensitive cookie without HttpOnly attribute
breadcrumbs:
- doc
- user... |
https://docs.gitlab.com/user/application_security/dast/browser/798.47 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.47.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.47.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Flutterwave test encrypted key | null |
## Description
The response body contains content that matches the pattern of a test Flutterwave encryption key was identified. This key is only used with the [direct charge endpoint](https://developer.flutterwave.com/docs/direct-card-charge). This key is used to encrypt payloads of card details prior to sending. Mo... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Flutterwave test encrypted k... |
https://docs.gitlab.com/user/application_security/dast/browser/798.135 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.135.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.135.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token DigitalOcean OAuth access token | null |
## Description
The response body contains content that matches the pattern of a DigitalOcean OAuth Access Token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please 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 DigitalOcean OAuth access to... |
https://docs.gitlab.com/user/application_security/dast/browser/798.149 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.149.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.149.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token GitLab incoming email token | null |
## Description
The response body contains content that matches the pattern of a GitLab incoming email token was identified. Your incoming email token authenticates you when you create a new issue by email, and is included in your personal project-specific email addresses. It cannot be used to access any other data. ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token GitLab incoming email token
... |
https://docs.gitlab.com/user/application_security/dast/browser/798.7 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.7.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.7.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Alibaba AccessKey ID | null |
## Description
The response body contains content that matches the pattern of a Alibaba AccessKey ID.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Alibaba AccessKey ID
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/16.11 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.11.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.11.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | TRACE HTTP method enabled | null |
## Description
The debug TRACE method was found to be enabled on the target web server. This
HTTP method reflects HTTP request data back to the user in a response. In some circumstances
this information may include sensitive data that is applied by intermediary proxies.
## Remediation
The TRACE HTTP method is for ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: TRACE HTTP method enabled
breadcrumbs:
- doc
- user
- application_sec... |
https://docs.gitlab.com/user/application_security/dast/browser/798.133 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.133.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.133.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Contentful preview API token | null |
## Description
The response body contains content that matches the pattern of a Contentful preview API token was identified. A preview API token maintains the same behavior and parameters as the Content Delivery API (CDA), but delivers the latest drafts for entries and assets. The Content Preview API is used to disp... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Contentful preview API token... |
https://docs.gitlab.com/user/application_security/dast/browser/94.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/94.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 94.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Server-side code injection (PHP) | null |
## Description
The target application was found vulnerable to code injection. A malicious actor could inject arbitrary
PHP code to be executed on the server. This could lead to a full system compromise by accessing
stored secrets, injecting code to take over accounts, or executing OS commands.
## Remediation
Never... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Server-side code injection (PHP)
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/dast/browser/798.159 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.159.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.159.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Artifactory Identity Token | null |
## Description
The response body contains content that matches the pattern of an Artifactory Identity Token was identified. An Artifactory Identity Token allows authentication to access repositories, download artifacts, upload artifacts, and execute privileged operations within JFrog Artifactory based on the token's... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Artifactory Identity Token
b... |
https://docs.gitlab.com/user/application_security/dast/browser/798.169 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.169.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.169.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Segment public API token | null |
## Description
The response body contains content that matches the pattern of a Segment Public API token was identified. The Segment Public API is used to manage your Segment workspaces and its resources. Two types of tokens match this pattern, a workspace owner token and a limited role token. In general these 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 Segment public API token
bre... |
https://docs.gitlab.com/user/application_security/dast/browser/798.61 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.61.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.61.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Intercom API token | null |
## Description
The response body contains content that matches the pattern of a Intercom API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Intercom API token
breadcrum... |
https://docs.gitlab.com/user/application_security/dast/browser/829.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/829.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 829.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Inclusion of Functionality from Untrusted Control Sphere | null |
## Description
JavaScript or CSS source files are included from third party domains without
[Sub-Resource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity).
If an attacker were to compromise the sites hosting these third party resources, they could inject malicious
script ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Inclusion of Functionality from Untrusted Control Sphere
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.67 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.67.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.67.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Linear client secret or ID (OAuth 2.0) | null |
## Description
The response body contains content that matches the pattern of an OAuth 2.0 Linear client secret or ID was identified. Client secrets are used when allowing users to sign in to your application. Depending on the scopes requested, a malicious actor could impersonate the service to access a user's infor... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Linear client secret or ID (... |
https://docs.gitlab.com/user/application_security/dast/browser/352.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/352.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 352.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Absence of anti-CSRF tokens | null |
## Description
The application failed to protect against Cross-Site Request Forgery (CSRF) by using
secure application tokens or `SameSite` cookie directives.
The vulnerability can be exploited by an attacker creating a link or form on a third
party site and tricking an authenticated victim to access them.
## Reme... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Absence of anti-CSRF tokens
breadcrumbs:
- doc
- user
- application_s... |
https://docs.gitlab.com/user/application_security/dast/browser/798.105 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.105.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.105.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Shopify personal access token | null |
## Description
The response body contains content that matches the pattern of a Shopify personal access token was identified. Access tokens can be given restricted scopes or be given full access to all store data. A malicious actor who gained access to this token could be able to read or modify store data.
Exposing ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Shopify personal access toke... |
https://docs.gitlab.com/user/application_security/dast/browser/798.179 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.179.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.179.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Stripe publishable test key | null |
## Description
The response body contains content that matches the pattern of a Stripe publishable test key was identified.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Stripe publishable test key
... |
https://docs.gitlab.com/user/application_security/dast/browser/89.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/89.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 89.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | SQL Injection | null |
## Description
It is possible to execute arbitrary SQL commands on the target application server's
backend database.
SQL Injection is a critical vulnerability that can lead to a data or system
compromise.
## Remediation
Always use parameterized queries when issuing requests to backend database systems. In
situatio... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: SQL Injection
breadcrumbs:
- doc
- user
- application_security
- dast... |
https://docs.gitlab.com/user/application_security/dast/browser/798.71 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.71.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.71.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Lob publishable API key | null |
## Description
The response body contains content that matches the pattern of a Lob Publishable API key was identified. Publishable API keys are only used for US verifications, international verifications, and US autocomplete requests. A malicious actor with access to this key can execute limited functions under you... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Lob publishable API key
brea... |
https://docs.gitlab.com/user/application_security/dast/browser/798.96 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.96.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.96.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token PyPi upload token | null |
## Description
The response body contains content that matches the pattern of a PyPi upload token was identified. Upload tokens are used for uploading packages for publishing Python packages. A malicious actor with access to this token can upload potentially malicious artifacts.
Exposing this value could allow attac... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token PyPi upload token
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.90 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.90.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.90.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token PlanetScale password | null |
## Description
The response body contains content that matches the pattern of a PlanetScale password was identified. PlanetScale passwords are used to connect to database instances. A malicious actor with access to this password can access PlanetScale managed databases..
Exposing this value could allow attackers to ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token PlanetScale password
breadcr... |
https://docs.gitlab.com/user/application_security/dast/browser/209.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/209.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 209.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Generation of error message containing sensitive information | null |
## Description
The application was found to return error data such as stack traces. Depending on the data contained within the error message,
this information could be used by an attacker to conduct further attacks. While stack traces are helpful during development
and debugging, they should not be presented to user... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Generation of error message containing sensitive information
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.173 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.173.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.173.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token SSH (DSA) private key | null |
## Description
The response body contains content that matches the pattern of an SSH private key was identified. Private SSH keys are used for authentication and symmetric key exchange. A malicious actor with access to this key can use it to impersonate an application or service.
Exposing this value could allow atta... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token SSH (DSA) private key
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.109 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.109.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.109.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Slack bot user OAuth token | null |
## Description
The response body contains content that matches the pattern of a Slack bot user OAuth token was identified. A Slack app's capabilities and permissions are governed by the scopes it requests. A full list of permissions can be found [in Slack's scopes documentation](https://api.slack.com/scopes). A mali... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Slack bot user OAuth token
b... |
https://docs.gitlab.com/user/application_security/dast/browser/798.175 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.175.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.175.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Stripe live restricted key | null |
## Description
The response body contains content that matches the pattern of a Stripe live restricted key was identified. Restricted keys offer greater security by only allowing read or write access to specific API resources. A malicious actor with access to this key is limited by the scope defined for the key.
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 Stripe live restricted key
b... |
https://docs.gitlab.com/user/application_security/dast/browser/798.163 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.163.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.163.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Onfido Live API Token | null |
## Description
The response body contains content that matches the pattern of an Onfido Live API Token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Onfido Live API Token
breadc... |
https://docs.gitlab.com/user/application_security/dast/browser/798.184 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.184.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.184.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Yandex Cloud AWS API compatible access secret | null |
## Description
The response body contains content that matches the pattern of Yandex Cloud AWS API compatible Access Secret.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked key... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Yandex Cloud AWS API compati... |
https://docs.gitlab.com/user/application_security/dast/browser/16.6 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/16.6.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 16.6.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | AspNetMvc header exposes version information | null |
## Description
The target website returns AspNet headers along with version information of this website. By
exposing these values attackers may attempt to identify if the target software is vulnerable to known
vulnerabilities. Or catalog known sites running particular versions to exploit in the future when a
vulnera... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: AspNetMvc header exposes version information
breadcrumbs:
- doc
- use... |
https://docs.gitlab.com/user/application_security/dast/browser/798.165 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.165.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.165.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token password in URL | null |
## Description
The response body contains content that matches the pattern of a password in URL.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab doc... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token password in URL
breadcrumbs:... |
https://docs.gitlab.com/user/application_security/dast/browser/798.182 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.182.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.182.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Yandex Cloud IAM cookie v1-2 | null |
## Description
The response body contains content that matches the pattern of Yandex Cloud IAM Token v1.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Yandex Cloud IAM cookie v1-2... |
https://docs.gitlab.com/user/application_security/dast/browser/798.17 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.17.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.17.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Beamer API token | null |
## Description
The response body contains content that matches the pattern of a Beamer API token was detected. Beamer API tokens can be used to read, write, and delete posts, and "ideas" as well as see NPS analytical reports. This service is used to notify users of changes to your software with email or other method... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Beamer API token
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.11 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.11.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.11.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Atlassian API token | null |
## Description
The response body contains content that matches the pattern of a Atlassian API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Atlassian API token
breadcru... |
https://docs.gitlab.com/user/application_security/dast/browser/798.27 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.27.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.27.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Discord client ID | null |
## Description
The response body contains content that matches the pattern of a Discord client ID was identified. Client IDs are used in OAuth applications and are used in combination with a client secret. This value alone does not grant any access and must be used alongside the client secret value.
Exposing this va... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Exposure of confidential secret or token Discord client ID
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.153 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.153.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.153.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Grafana API token | null |
## Description
The response body contains content that matches the pattern of a Grafana API token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the GitLab 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 Grafana API token
breadcrumb... |
https://docs.gitlab.com/user/application_security/dast/browser/798.155 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.155.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.155.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token Instagram access token | null |
## Description
The response body contains content that matches the pattern of an Instagram access token.
Exposing this value could allow attackers to gain access to all resources granted by this token.
## Remediation
For general guidance on handling security incidents with regards to leaked keys, please see the 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 Instagram access token
bread... |
https://docs.gitlab.com/user/application_security/dast/browser/113.1 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/113.1.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 113.1.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Improper Neutralization of CRLF Sequences in HTTP Headers | null |
## Description
By inserting Carriage Return / Line Feed (CRLF) characters, malicious users could potentially inject arbitrary data into HTTP responses. By modifying HTTP responses, attackers could conduct cross-site scripting or cache poisoning attacks against other users of the system.
## Remediation
User input 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: Improper Neutralization of CRLF Sequences in HTTP Headers
breadcrumbs... |
https://docs.gitlab.com/user/application_security/dast/browser/798.37 | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/798.37.md | 2025-08-13 | doc/user/application_security/dast/browser/checks | [
"doc",
"user",
"application_security",
"dast",
"browser",
"checks"
] | 798.37.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Exposure of confidential secret or token EasyPost test API key | null |
## Description
The response body contains content that matches the pattern of an EasyPost test API key was identified. Test API keys are used for functionality testing. A malicious actor with access to this key can only use limited functionality of the EasyPost service.
Exposing this value could allow attackers to 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 EasyPost test API key
breadc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.