Injection vulnerabilities

Injection vulnerabilities are a type of security-related rules, that can be raised by both SonarQube Server and SonarQube Cloud. 

Due to technical limitations, SonarQube for IDE can not raise injection vulnerabilities on local analysis and instead pulls them from SonarQube (Server, Cloud) following a project analysis. Because SonarLint must pull injection vulnerabilities from SonarQube Server or SonarQube Cloud, the use of connected mode is required.

Prerequisites

• You need to bind to SonarQube Cloud or SonarQube Server 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 SonarQube Cloud, you must work with long-lived branches. Issues on short-lived branches are not synchronized; SonarQube Server does not distinguish between long- and short-lived branches. 

How to display injection vulnerabilities

1. Bind your project to SonarQube (Server, Cloud) using Connected Mode.
2. Open the SonarQube for IDE tool window and select the Taint Vulnerabilities tab.
3. The tab should display the list of injection vulnerabilities that are present on open files.

How to fix your injection vulnerabilities

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

Because the detection of injection vulnerabilities requires that you are run in Connected Mode, any changes you make to the code must be resolved by your SonarQube (Server, Cloud) instance. Here are two options to resolve injection vulnerabilities displayed by SonarQube for IDE:

• If you fix the issue locally, commit your code to the server and rerun the analysis on SonarQube (Server, Cloud). The new status (of the issue) will show up automatically in your local analysis.
• If you go to the issue in SonarQube (Server, Cloud) 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 injection vulnerabilities in IntelliJ.