SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • GroovyGroovy
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
VB.NET

VB.NET static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your VB.NET code

  • All rules 238
  • Vulnerability34
  • Bug44
  • Security Hotspot16
  • Code Smell144

  • Quick Fix 11
Filtered: 2 rules found
sql
    Impact
      Clean code attribute
        1. Database queries should not be vulnerable to injection attacks

           Vulnerability
        2. Formatting SQL queries is security-sensitive

           Security Hotspot

        Formatting SQL queries is security-sensitive

        intentionality - complete
        maintainability
        security
        Security Hotspot
        • cwe
        • bad-practice
        • sql

        Formatted SQL queries can be difficult to maintain, debug and can increase the risk of SQL injection when concatenating untrusted values into the query. However, this rule doesn’t detect SQL injections, the goal is only to highlight complex/formatted queries.

        Ask Yourself Whether

        • Some parts of the query come from untrusted values (like user inputs).
        • The query is repeated/duplicated in other parts of the code.
        • The application must support different types of relational databases.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Use parameterized queries, prepared statements, or stored procedures and bind variables to SQL query parameters.
        • Consider using ORM frameworks if there is a need to have an abstract layer to access data.

        Sensitive Code Example

        Public Sub SqlCommands(ByVal connection As SqlConnection, ByVal query As String, ByVal param As String)
            Dim sensitiveQuery As String = String.Concat(query, param)
            command = New SqlCommand(sensitiveQuery) ' Sensitive
        
            command.CommandText = sensitiveQuery ' Sensitive
        
            Dim adapter As SqlDataAdapter
            adapter = New SqlDataAdapter(sensitiveQuery, connection) ' Sensitive
        End Sub
        
        Public Sub Foo(ByVal context As DbContext, ByVal query As String, ByVal param As String)
            Dim sensitiveQuery As String = String.Concat(query, param)
            context.Database.ExecuteSqlCommand(sensitiveQuery) ' Sensitive
        
            context.Query(Of User)().FromSql(sensitiveQuery) ' Sensitive
        End Sub
        

        Compliant Solution

        Public Sub Foo(ByVal context As DbContext, ByVal value As String)
            context.Database.ExecuteSqlCommand("SELECT * FROM mytable WHERE mycol=@p0", value) ' Compliant, the query is parameterized
        End Sub
        

        See

        • OWASP - Top 10 2021 Category A3 - Injection
        • OWASP - Top 10 2017 Category A1 - Injection
        • CWE - CWE-20 - Improper Input Validation
        • CWE - CWE-89 - Improper Neutralization of Special Elements used in an SQL Command
        • Derived from FindSecBugs rules Potential SQL/JPQL Injection (JPA), Potential SQL/JDOQL Injection (JDO), Potential SQL/HQL Injection (Hibernate)
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2026 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use