diff --git a/docs/.gitbook/assets/project_details_fixes.png b/docs/.gitbook/assets/project_details_fixes.png new file mode 100644 index 000000000000..4b6755138c8d Binary files /dev/null and b/docs/.gitbook/assets/project_details_fixes.png differ diff --git a/docs/.gitbook/assets/project_details_linkto_snyk_vuln_database.png b/docs/.gitbook/assets/project_details_linkto_snyk_vuln_database.png new file mode 100644 index 000000000000..57ed92b66864 Binary files /dev/null and b/docs/.gitbook/assets/project_details_linkto_snyk_vuln_database.png differ diff --git a/docs/.gitbook/assets/project_details_transitive_dependency_no_fix (1).png b/docs/.gitbook/assets/project_details_transitive_dependency_no_fix (1).png new file mode 100644 index 000000000000..26472b64033c Binary files /dev/null and b/docs/.gitbook/assets/project_details_transitive_dependency_no_fix (1).png differ diff --git a/docs/.gitbook/assets/project_details_transitive_dependency_no_fix (2).png b/docs/.gitbook/assets/project_details_transitive_dependency_no_fix (2).png new file mode 100644 index 000000000000..b834b7f9af54 Binary files /dev/null and b/docs/.gitbook/assets/project_details_transitive_dependency_no_fix (2).png differ diff --git a/docs/.gitbook/assets/project_details_transitive_dependency_no_fix.png b/docs/.gitbook/assets/project_details_transitive_dependency_no_fix.png new file mode 100644 index 000000000000..bee0bc59ce85 Binary files /dev/null and b/docs/.gitbook/assets/project_details_transitive_dependency_no_fix.png differ diff --git a/docs/.gitbook/assets/projects_issues_scan_results.png b/docs/.gitbook/assets/projects_issues_scan_results.png new file mode 100644 index 000000000000..538893078221 Binary files /dev/null and b/docs/.gitbook/assets/projects_issues_scan_results.png differ diff --git a/docs/.gitbook/assets/snyk_vuln_database_how_to_fix.png b/docs/.gitbook/assets/snyk_vuln_database_how_to_fix.png new file mode 100644 index 000000000000..cf554741f2ca Binary files /dev/null and b/docs/.gitbook/assets/snyk_vuln_database_how_to_fix.png differ diff --git a/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/fix-your-vulnerabilities.md b/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/fix-your-vulnerabilities.md index 6ec7eca87400..cbd800568f61 100644 --- a/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/fix-your-vulnerabilities.md +++ b/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/fix-your-vulnerabilities.md @@ -17,7 +17,7 @@ From Snyk Open Source, for each tab, both upgrade and patch, in the fix advice a * Packages are listed and can be expanded to show the full list of vulnerabilities affecting the package. * All the vulnerabilities found in your dependencies are displayed further down the page, together with contextual information that can help you prioritize the issues and start fixing them if required. -
Scan results on the Web UI

Scan results on the Web UI

+

Example of project issues

## View Fix Advice @@ -30,11 +30,9 @@ The Fix Advice area appears on the Project details page. Snyk offers you one of The summary area groups advice by package, and is displayed based on the best available fix. Advice in these summary lists includes these details for each package: * All vulnerability names and severity details affecting that package -* The recommended fix, a link to the recommended fix for this package and its listed vulnerabilities: either the specific version to which to upgrade or the name of the patch +* The recommended fix, a link to the recommended fix for this package and its listed vulnerabilities: either the specific version to which to upgrade or the name of the patch. -
Upgrade issues tabs

Upgrade issues tabs

- -
Upgradable and patchable issues tabs

Upgradable and patchable issues tabs

+

Upgradable issues tab

You can also find additional advice and details further down on the Project details page: diff --git a/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/gatekeeper-plugins/nexus-repository-manager-gatekeeper-plugin.md b/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/gatekeeper-plugins/nexus-repository-manager-gatekeeper-plugin.md index 664935449793..b34174c49433 100644 --- a/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/gatekeeper-plugins/nexus-repository-manager-gatekeeper-plugin.md +++ b/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/gatekeeper-plugins/nexus-repository-manager-gatekeeper-plugin.md @@ -78,7 +78,7 @@ After the plugin is installed, every time a developer requests a download of an
Results of a scan

Results of a scan

-
Attributes showing results of a scan

Attributes showing results of a scan

+
Example of results of a scan

Attributes displaying results of a scan

By reviewing the results, you can evaluate the issues found in your artifact and determine a course of action. @@ -104,6 +104,6 @@ Snyk continuously runs in the background on the Nexus instance, and whenever any When the scan ends, you get an error message if the download was blocked, with a link to the full details for the known vulnerabilities found in that artifact, similar to the following example: -
Error message example

Error message example

+

Error message example

Click the link to view the number of vulnerabilities found in the artifact and their severities. diff --git a/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/vulnerability-fix-types.md b/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/vulnerability-fix-types.md index e41888d515f9..ae42842a7791 100644 --- a/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/vulnerability-fix-types.md +++ b/docs/scan-with-snyk/snyk-open-source/manage-vulnerabilities/vulnerability-fix-types.md @@ -29,9 +29,9 @@ The Fix this vulnerability option is not available in CLI monitor workflows. For any **fixable** issue in a Project where **Fix this vulnerability** is available, Snyk can open a pull request against the repository to update to a secure version of the dependency. -Look for the **Fix this vulnerability** button on the issue card to determine whether Snyk can open a pull request against your Project. Examine the i**ssue cards** to see the specifics of fixability for an issue. +The **Fix this vulnerability** button on the issue card displays whether Snyk can open a pull request against your Project. Examine the issue cards to see the specifics of fixability for an issue. -
Fixable vulnerabiltiies

Fixable vulnerability

+

Example of a fixable vulnerability

### Partially fixable @@ -43,13 +43,13 @@ You can view the **Partially fixed** vulnerabilities for an issue in the Detaile The option to partially fix vulnerabilities is available only for JavaScript and TypeScript. {% endhint %} -
Partially fixable vulnerability

Partially fixable vulnerability

+

Example of a partially fixable vulnerability

### No supported fix If there is **No supported fix** for the vulnerabilities or license issues, then the issue cards do not show any Fix options. An upgrade path where the only changes are in transitive dependencies is considered fixable only if the package manager supports it. -
Vulnerability with no supported fix

Vulnerability with no supported fix

+

Example of a vulnerability with no supported fix

## "**Fixed in" Available filters** @@ -60,15 +60,15 @@ In the "Fixed in" Available filters, you can use the following filters: You can view the **Fixed in** information for vulnerabilities on the issue card. This indicates the version of the package that no longer has the vulnerability. -
Fised in information on issues card

Fixed in information on issues card

+

Fixed in information on an issue card

### Why is `Fixed in` showing when the issue is not fixable? A direct dependency is fixable if a fixed, that is, secure, version of the package exists anywhere in the system. However, to be fixable, transitive dependencies must have a direct dependency that can be updated to the fixed version of the transitive dependency. An example follows of a transitive dependency. -
Transitive dependency shown as Fixed in

Transitive dependency shown as Fixed in

+

Example of a transitive dependency

-The Detailed paths section (rounded blue rectangle in the image) shows that no remediation path is available. However, the issue card shows that the vulnerability is Fixed in the more recent version (top red rectangle in the image). Snyk does not have the ability to reach the level where the vulnerability exists in this specific Project, but the vulnerability does not match the definition of No supported fix. +Under **Detailed paths,** a mention is displayed that no remediation path is available. However, the issue card shows that the vulnerability is **Fixed in** the more recent version. Snyk does not have the ability to reach the level where the vulnerability exists in this specific Project, but the vulnerability does not match the definition of No supported fix. ### Fixing transitive dependencies @@ -78,11 +78,11 @@ You cannot automatically fix transitive dependencies or open a Fix PR (see [Fix To fix a transitive dependency like the one in this example, follow the link to the [Snyk Vulnerability Database](snyk-vulnerability-database.md): -
LInk to Snyk Vulnerability Database for a transitive dependency

LInk to Snyk Vulnerability Database for a transitive dependency

+
Link to Snyk Vulnerability Database for a transitive dependency

LInk to Snyk Vulnerability Database for a transitive dependency

From the Snyk Vulnerability Database, you can see remediation advice for more fix information: -
Vulnerability Database remediation advice

Vulnerability Database remediation advice

+

Snyk Vulnerability Database remediation advice

### Fixing transitive dependencies through direct dependencies diff --git a/docs/scan-with-snyk/snyk-open-source/package-repository-integrations/artifactory-package-repository-connection-setup/README.md b/docs/scan-with-snyk/snyk-open-source/package-repository-integrations/artifactory-package-repository-connection-setup/README.md index f3166f96e3fd..ef4d137d4e7a 100644 --- a/docs/scan-with-snyk/snyk-open-source/package-repository-integrations/artifactory-package-repository-connection-setup/README.md +++ b/docs/scan-with-snyk/snyk-open-source/package-repository-integrations/artifactory-package-repository-connection-setup/README.md @@ -24,4 +24,4 @@ The steps to set up Artifactory Repository Manager follow. 3. Enter your username and password. 4. Select **Save**. -
Artifactory repository setup

Artifactoryrepository setup

+
Artifactory repository setup

Artifactory repository setup