Taint vulnerabilities

Injection vulnerabilities are a type of security-related rules, that can be raised by both SonarCloud and SonarQube (starting with Developer Edition). 

Due to technical limitations, SonarLint can not raise injection vulnerabilities on local analysis and instead pulls them from SonarQube or SonarCloud following a project analysis. Because SonarLint must pull injection vulnerabilities from SonarQube or SonarCloud, the use of Connected Mode is required.

Prerequisites

• You need to bind to SonarCloud or SonarQube Developer Edition (or higher) 8.9+
• For this feature to be valuable, your project needs to be analyzed frequently (ideally by your CI server when pushing new code)
• Only issues detected on open files will be displayed in the IDE
• Only issues detected on the main branch will be displayed in the IDE
• When running in Connected Mode with SonarCloud, you must work with long-lived branches. Issues on short-lived branches are not synchronized; SonarQube does not distinguish between long- and short-lived branches. 

How to display taint vulnerabilities

1. Bind your project to SonarQube or SonarCloud using Connected Mode.
2. Open the SonarLint tool window and select the Taint Vulnerabilities tab.
3. The tab should display the list of taint vulnerabilities that are present on open files.

How to fix your taint issues

Taint vulnerabilities are security-related rule issues that are only raised by SonarQube (starting with Developer Edition) and SonarCloud. Due to technical limitations, SonarLint can not raise such issues on local analysis. 

Because the detection of taint issues requires that you are run in Connected Mode, any changes you make to the code must be resolved by your SonarQube or SonarCloud instance. Here are two options to resolve taint issues displayed by SonarLint:

• If you fix the issue locally, commit your code to the server and rerun the analysis on SonarQube or SonarCloud. The new status (of the issue) will show up automatically in your local analysis.
• If you go to the issue in SonarQube or SonarCloud and mark it as fixed, false positive, or won’t fix, in less than 1 minute, the new status will be updated locally.

Check the Fixing issues page for complete details about dealing with taint vulnerabilities in IntelliJ.