Reachable vulnerabilities
Snyk reachable vulnerability scanning allows you to gauge risk by identifying whether a function related to the vulnerability is being called by your application, raising the chances of that vulnerability being exploitable in the context of your application.
Reachable vulnerabilities can be used as a single signal to make decisions or as part of a broader risk-based prioritization approach, like the Risk Score.
The following instructions explain how to set up and use reachable vulnerabilities, as well as provide more information on how reachability analysis works at Snyk.
Set up reachable vulnerability analysis
To set up reachable vulnerabilities analysis:
In the Organization settings, navigate to the Languages section.
Navigate to the Reachable vulnerabilities section.
Activate Reachable vulnerabilities analysis and save your changes.
After it is enabled, reachable vulnerabilities analysis is done as part of scanning Projects.
To update existing Projects with the reachability analysis immediately, trigger a manual test.
Supported languages and integrations for Reachable Vulnerabilities
Reachable vulnerabilities analysis is available for Java (Maven and Gradle) Projects.
The following integrations are supported for Reachable Vulnerabilities analysis:
Bitbucket Cloud (Currently in Early Access)
Bitbucket Server (Currently in Early Access)
GitLab (Currently in Early Access)
Azure Repos (Currently in Early Access)
Brokered connections (Currently in Early Access)
Release status
Reachability for all SCM providers is in Early Access and available only for Enterprise plans.
To enable the feature, see Snyk Preview.
Reachable vulnerability analysis using the Snyk CLI, other Git integrations, and other languages is not currently supported.
Enabling Reachability for brokered connections
If you use a brokered connection to your SCM, configure the Broker to provide access to your source files. See the Snyk Code - Clone capability with Broker for Docker, the Broker rules for Snyk Code, and the Snyk Broker - Code Agent documentation for configuration details when the Broker is used with Snyk Code.
Using Reachability
Reachability status
After a vulnerability is identified, it has a reachability status
Reachable - A direct or indirect path was found from your application to the vulnerable code.
No path found - No path found from your application to the vulnerable code.
If a no path found status is given, do not assume that the vulnerability is totally unreachable or unexploitable.
Reachability status is available on the Project page, as part of the Risk Score, in the Issues Detail report, and through the Get issues by group ID API.
Reachability as shown on the Project page
After you import or test a Project using the Snyk UI, the Project is monitored by Snyk, and the results of the reachable vulnerabilities analysis appear on the Project page in the following places:
Filters - Allows you to focus on reachable vulnerabilities first by filtering results based on reachability.
Reachability badge - Allows you to quickly understand the reachability level of vulnerabilities.
Call path - Allows you to see the path from your code to the vulnerable function to validate the result.
Reachability as part of the Risk Score
Risk Score helps you apply holistic Risk-Based prioritization that combines multiple factors, associated with either the vulnerability or the context of your application. Reachability is such a contextual factor that will significantly increase the overall score.
Risk Score is available on the Projects page and through the API and Reports.
Priority score, the legacy model preceding the Risk Score, also takes reachable vulnerabilities into account.
Reachable vulnerability analysis
Snyk uses a combination of security expert analysis, program analysis, and various AI techniques to determine the reachability of a vulnerability, including these steps of analysis:
Enriching vulnerabilities with the patches applied to fix them - as part of the Snyk vulnerability curation process, Snyk references the fix commit that the maintainer applied.
Related elements analysis- Based on the commit fix, Snyk uses DeepCode AI program analysis to analyze the functions and other elements related to the vulnerability.
Root Cause analysis - Snyk uses DeepCode AI and NLP techniques to automatically rank the related code elements by their chances of being the root cause of the vulnerability.
Reachability analysis - As issues are found in your application by a Snyk scan, the DeepCode program analysis engine is used to analyze the call graph of your application in relation to the call graph between the open-source dependencies used. A path between your application and a code element ranked as a root cause will yield a “Reachable” vulnerability.
Security experts supervision - Snyk security experts will manually verify and mark elements as root causes in order to make the entire analysis more accurate over time
The following considerations related to false positives and false negatives apply to Reachble vulnerability analysis.
Program analysis requires a trade-off between accurate results (minimizing false positives) and recall rates (not missing potentially exploitable vulnerabilities).
To facilitate this trade-off, Snyk DeepCode analysis applies real-time decision-making to determine whether to under-approximate the set of reachable elements based on analysis of the likelihood a reachable path will be found in a specific environment.
For example, it is not always possible to give a precise answer when reflection programming is used. In such a case, neither returning a large set of false positives nor returning “Not reachable” will suffice. Snyk Deep Code analysis optimizes in order to retrieve the most accurate and complete result possible for a given code structure.
Last updated
