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
ABAP

ABAP static code analysis

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

  • All rules 94
  • Vulnerability4
  • Bug14
  • Security Hotspot7
  • Code Smell69
 
Tags
    Impact
      Clean code attribute
        1. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        2. Using shell interpreter when executing OS commands is security-sensitive

           Security Hotspot
        3. Using "CALL TRANSACTION" statements without an authority check is security-sensitive

           Security Hotspot
        4. Hard-coded credentials are security-sensitive

           Security Hotspot
        5. Having dynamic clauses for SQL "SELECT" statements is security-sensitive

           Security Hotspot
        6. Having SQL "SELECT" statements without "WHERE" conditions is security-sensitive

           Security Hotspot
        7. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Having SQL "SELECT" statements without "WHERE" conditions is security-sensitive

        intentionality - efficient
        security
        Security Hotspot
        • performance
        • sql

        Although the WHERE condition is optional in a SELECT statement, for performance and security reasons, a WHERE clause should always be specified to prevent reading the whole table.

        Ask Yourself Whether

        • The whole table is not required.
        • The table contains sensitive information.

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

        Recommended Secure Coding Practices

        Add a "WHERE" condition to "SELECT" statements.

        Sensitive Code Example

        SELECT * FROM db_persons INTO us_persons.
        

        Compliant Solution

        SELECT * FROM db_persons INTO us_persons WHERE country IS 'US'.
        

        Exceptions

        SELECT SINGLE and UP TO 1 ROWS result in only one record being read, so such SELECTs are ignored by this rule.

        SELECT SINGLE * FROM db_persons INTO us_persons.
        
        SELECT * FROM db_persons UP TO 1 ROWS INTO us_persons.
        
          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 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