You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/development/testing_guide/end_to_end/best_practices/rspec_metadata_tests.md
-1
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,6 @@ This is a partial list of the [RSpec metadata](https://rspec.info/features/3-12/
44
44
|`:requires_admin`| The test requires an administrator account. Tests with the tag are excluded when run against Canary and Production environments. |
45
45
|`:requires_git_protocol_v2`| The test requires that Git protocol version 2 is enabled on the server. It's assumed to be enabled by default but if not the test can be skipped by setting `QA_CAN_TEST_GIT_PROTOCOL_V2` to `false`. |
46
46
|`:requires_praefect`| The test requires that the GitLab instance uses [Gitaly Cluster](../../../../administration/gitaly/praefect.md) (a.k.a. Praefect) as the repository storage. It's assumed to be used by default but if not the test can be skipped by setting `QA_CAN_TEST_PRAEFECT` to `false`. |
47
-
|`:runner`| The test depends on and sets up a GitLab Runner instance, typically to run a pipeline. |
48
47
|`:skip_live_env`| The test is excluded when run against live deployed environments such as Staging, Canary, and Production. |
49
48
|`:skip_fips_env`| The test is excluded when run against an environment in FIPS mode. |
50
49
|`:skip_signup_disabled`| The test uses UI to sign up a new user and is skipped in any environment that does not allow new user registration via the UI. |
Copy file name to clipboardExpand all lines: doc/user/application_security/dependency_list/_index.md
+12-1
Original file line number
Diff line number
Diff line change
@@ -52,21 +52,32 @@ Although this is not mandatory for populating the dependency list, the SBOM docu
52
52
53
53
- In GitLab 17.2, the `location` field no longer links to the commit where the dependency was last detected when the feature flag `skip_sbom_occurrences_update_on_pipeline_id_change` is enabled. The flag is disabled by default.
54
54
- In GitLab 17.3 the `location` field always links to the commit where the dependency was first detected. Feature flag `skip_sbom_occurrences_update_on_pipeline_id_change` removed.
55
+
- View dependency paths option [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/519965) in GitLab 17.11 [with a flag](../../../administration/feature_flags.md) named `dependency_paths`. Disabled by default.
55
56
56
57
{{< /history >}}
57
58
59
+
{{< alert type="flag" >}}
60
+
61
+
The availability of this feature is controlled by a feature flag.
62
+
For more information, see the history.
63
+
64
+
{{< /alert >}}
65
+
58
66
To view the dependencies of a project or all projects in a group:
59
67
60
68
1. On the left sidebar, select **Search or go to** and find your project or group.
61
69
1. Select **Secure > Dependency list**.
70
+
1. Optional. If there are transitive dependencies, you can also view all of the dependency paths:
71
+
- For a project, in the **Location** column, select **View dependency paths**.
72
+
- For a group, in the **Location** column, select the location, then select **View dependency paths**.
62
73
63
74
Details of each dependency are listed, sorted by decreasing severity of vulnerabilities (if any). You can sort the list instead by component name, packager, or license.
64
75
65
76
| Field | Description |
66
77
|:----------|:-----------|
67
78
| Component | The dependency's name and version. |
68
79
| Packager | The packager used to install the dependency. |
69
-
| Location | For system dependencies, this lists the image that was scanned. For application dependencies, this shows a link to the packager-specific lock file in your project that declared the dependency. It also shows the [direct dependents](#dependency-paths) of the dependency, if any, and if supported. |
80
+
| Location | For system dependencies, this field lists the image that was scanned. For application dependencies, this field shows a link to the packager-specific lock file in your project that declared the dependency. It also shows the direct [dependents](#dependency-paths), if any. If there are transitive dependencies, selecting **View dependency paths** shows the full path of all dependents. Transitive dependencies are indirect dependents that have a direct dependent as an ancestor. |
70
81
| License (for projects only) | Links to dependency's software licenses. A warning badge that includes the number of vulnerabilities detected in the dependency. |
71
82
| Projects (for groups only) | Links to the project with the dependency. If multiple projects have the same dependency, the total number of these projects is shown. To go to a project with this dependency, select the **Projects** number, then search for and select its name. The project search feature is supported only on groups that have up to 600 occurrences in their group hierarchy. |
Copy file name to clipboardExpand all lines: doc/user/application_security/vulnerabilities/_index.md
+27-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ including:
21
21
- Available actions
22
22
- Linked issues
23
23
- Actions log
24
-
-Filename and line number of the vulnerability (if available)
24
+
-Location
25
25
- Severity
26
26
27
27
For vulnerabilities in the [Common Vulnerabilities and Exposures (CVE)](https://www.cve.org/)
@@ -571,3 +571,29 @@ To view the security training for a vulnerability:
571
571
1. Select **Secure > Vulnerability report**.
572
572
1. Select the vulnerability for which you want to view security training.
573
573
1. Select **View training**.
574
+
575
+
## View the location of a vulnerability in transitive dependencies
576
+
577
+
{{< history >}}
578
+
579
+
- View dependency paths option [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/519965) in GitLab 17.11 [with a flag](../../../administration/feature_flags.md) named `dependency_paths`. Disabled by default.
580
+
581
+
{{< /history >}}
582
+
583
+
{{< alert type="flag" >}}
584
+
585
+
The availability of this feature is controlled by a feature flag.
586
+
For more information, see the history.
587
+
588
+
{{< /alert >}}
589
+
590
+
When managing vulnerabilities found in dependencies in the vulnerability details, under **Location**, you can view:
591
+
592
+
- The location of the direct dependency where the vulnerability was found.
593
+
- If available, the specific line number where the vulnerability occurs.
594
+
595
+
If the vulnerability occurs in one or more transitive dependencies, knowing only the direct dependency may not be enough. Transitive dependencies are indirect dependencies that have a direct dependent as an ancestor.
596
+
597
+
If any transitive dependencies exist, you can view the paths to all dependencies, including the transitive dependencies that contain the vulnerability.
598
+
599
+
- On the vulnerability details page, under **Location**, select **View dependency paths**. If **View dependency paths** doesn't appear, then there are no transitive dependencies.
0 commit comments