Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
28b9c4cb
Commit
28b9c4cb
authored
Sep 04, 2020
by
Nicole Schwartz
Committed by
Nick Gaskill
Sep 04, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update interacting with vulns auto-remediation docs
parent
39290fed
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
24 deletions
+3
-24
doc/user/application_security/vulnerabilities/index.md
doc/user/application_security/vulnerabilities/index.md
+3
-24
No files found.
doc/user/application_security/vulnerabilities/index.md
View file @
28b9c4cb
...
...
@@ -23,7 +23,7 @@ several different ways:
-
[
Create issue
](
#creating-an-issue-for-a-vulnerability
)
- Create a new issue with the
title and description pre-populated with information from the vulnerability report.
By default, such issues are
[
confidential
](
../../project/issues/confidential_issues.md
)
.
-
[
Solution
](
#automatic-remediation-
solutions-
for-vulnerabilities
)
- For some vulnerabilities,
-
[
Solution
](
#automatic-remediation-for-vulnerabilities
)
- For some vulnerabilities,
a solution is provided for how to fix the vulnerability.
## Changing vulnerability status
...
...
@@ -47,28 +47,7 @@ project the vulnerability came from, and pre-populates it with useful informatio
the vulnerability report. After the issue is created, GitLab redirects you to the
issue page so you can edit, assign, or comment on the issue.
## Automatic remediation
solutions
for vulnerabilities
## Automatic remediation for vulnerabilities
You can fix some vulnerabilities by applying the solution that GitLab automatically
generates for you. GitLab supports the following scanners:
-
[
Dependency Scanning
](
../dependency_scanning/index.md
)
: Automatic Patch creation
is only available for Node.js projects managed with
`yarn`
.
-
[
Container Scanning
](
../container_scanning/index.md
)
.
When an automatic solution is available, the button in the header will show "Resolve with merge request":
![
Resolve with Merge Request button
](
img/vulnerability_page_merge_request_button_v13_1.png
)
Selecting the button will create a merge request with the automatic solution.
### Manually applying a suggested patch
To manually apply the patch that was generated by GitLab for a vulnerability, select the dropdown arrow on the "Resolve
with merge request" button, then select the "Download patch to resolve" option:
![
Resolve with Merge Request button dropdown
](
img/vulnerability_page_merge_request_button_dropdown_v13_1.png
)
This will change the button text to "Download patch to resolve". Click on it to download the patch:
![
Download patch button
](
img/vulnerability_page_download_patch_button_v13_1.png
)
generates for you.
[
Read more about the automatic remediation for vulnerabilities feature
](
../index.md#solutions-for-vulnerabilities-auto-remediation
)
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment