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
Filtered: 7 rules found
cwe
    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. "BREAK-POINT" statement should not be used in production

           Vulnerability
        7. "CASE" statements should have "WHEN OTHERS" clauses

           Code Smell

        "CASE" statements should have "WHEN OTHERS" clauses

        intentionality - clear
        maintainability
        Code Smell
        • cwe

        Why is this an issue?

        More Info

        The requirement for an OTHERS clause is defensive programming. The clause should either take appropriate action, or contain a suitable comment as to why no action is taken.

        Noncompliant code example

        CASE SY-INDEX.   // Noncompliant; missing WHEN OTHERS clause
          WHEN ONE.
            WRITE  'One'.
          WHEN 2.
            WRITE   'Two'.
        ENDCASE.
        

        Compliant solution

        CASE SY-INDEX.
          WHEN ONE.
            WRITE  'One'.
          WHEN 2.
            WRITE   'Two'.
          WHEN OTHERS. // Compliant
            WRITE 'Unexpected result'
        ENDCASE.
        
        CASE SY-INDEX.
          WHEN OTHERS.   // Compliant
            WRITE 'Unexpected result'
          WHEN ONE.
            WRITE  'One'.
          WHEN 2.
            WRITE   'Two'.
        ENDCASE.
        
          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