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
  • 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
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 8 rules found
sql
    Impact
      Clean code attribute
        1. Use batch Processing in JDBC

           Code Smell
        2. Constant parameters in a "PreparedStatement" should not be set more than once

           Code Smell
        3. SQL queries should retrieve only necessary fields

           Code Smell
        4. Avoid using "FetchType.EAGER"

           Code Smell
        5. Database queries should not be vulnerable to injection attacks

           Vulnerability
        6. "PreparedStatement" and "ResultSet" methods should be called with valid indices

           Bug
        7. "ResultSet.isLast()" should not be used

           Code Smell
        8. Formatting SQL queries is security-sensitive

           Security Hotspot

        Database queries should not be vulnerable to injection attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • sql
        • android
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Database injections (such as SQL injections) occur in an application when the application retrieves data from a user or a third-party service and inserts it into a database query without sanitizing it first.

        If an application contains a database query that is vulnerable to injections, it is exposed to attacks that target any database where that query is used.

        A user with malicious intent is able to modify the existing query to change its logic to a malicious one.

        After creating the malicious request, the attacker can attack the databases affected by this vulnerability without relying on any pre-requisites.

        What is the potential impact?

        In the context of a web application that is vulnerable to SQL injection:
        After discovering the injection, attackers inject data into the vulnerable field to execute malicious commands in the affected databases.

        Below are some real-world scenarios that illustrate some impacts of an attacker exploiting the vulnerability.

        Identity spoofing and data manipulation

        A malicious database query enables privilege escalation or direct data leakage from one or more databases. This threat is the most widespread impact.

        Data deletion and denial of service

        The malicious query makes it possible for the attacker to delete data in the affected databases.
        This threat is particularly insidious if the attacked organization does not maintain a disaster recovery plan (DRP).

        Chaining DB injections with other vulnerabilities

        Attackers who exploit SQL injections rely on other vulnerabilities to maximize their profits.
        Most of the time, organizations overlook some defense in depth measures because they assume attackers cannot reach certain points in the infrastructure. This misbehavior can lead to multiple attacks with great impact:

        • When secrets are stored unencrypted in databases: Secrets can be exfiltrated and lead to compromise of other components.
        • If server-side OS and/or database permissions are misconfigured, injection can lead to remote code execution (RCE).
          • See our article on this topic
          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use