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
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

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

  • All rules 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
 
Tags
    Impact
      Clean code attribute
        1. Accessing files should not introduce TOCTOU vulnerabilities

           Vulnerability
        2. Account validity should be verified when authenticating users with PAM

           Vulnerability
        3. "memset" should not be used to delete sensitive data

           Vulnerability
        4. POSIX functions should not be called with arguments that trigger buffer overflows

           Vulnerability
        5. Cipher algorithms should be robust

           Vulnerability
        6. Encryption algorithms should be used with secure mode and padding scheme

           Vulnerability
        7. Server hostnames should be verified during SSL/TLS connections

           Vulnerability
        8. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        9. Cryptographic keys should be robust

           Vulnerability
        10. Weak SSL/TLS protocols should not be used

           Vulnerability
        11. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        12. Insecure functions should not be used

           Vulnerability
        13. "scanf()" and "fscanf()" format strings should specify a field width for the "%s" string placeholder

           Vulnerability

        Account validity should be verified when authenticating users with PAM

        consistency - conventional
        security
        Vulnerability
        • cwe
        • symbolic-execution

        Pluggable authentication module (PAM) is a mechanism used on many UNIX variants to provide a unified way to authenticate users, independently of the underlying authentication scheme.

        Why is this an issue?

        How can I fix it?

        More Info

        When authenticating users, if the validity of the account is not checked (not locked, not expired …​), it may lead to unauthorized access to resources.

          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