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
C++

C++ static code analysis

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

  • All rules 798
  • Vulnerability14
  • Bug173
  • Security Hotspot19
  • Code Smell592

  • Quick Fix 99
Filtered: 110 rules found
cert
    Impact
      Clean code attribute
        1. "abort", "exit", "getenv" and "system" from <stdlib.h> should not be used

           Bug
        2. "atof", "atoi" and "atol" from <stdlib.h> should not be used

           Bug
        3. "setjmp" and "longjmp" should not be used

           Code Smell
        4. Reserved identifiers should not be defined or declared

           Code Smell
        5. In the definition of a function-like macro, each instance of a parameter shall be enclosed in parentheses, unless it is used as the operand of # or ##

           Code Smell
        6. Function-like macros should not be used

           Code Smell
        7. The address of an automatic object should not be assigned to another object that may persist after the first object has ceased to exist

           Bug
        8. Function exit paths should have appropriate return values

           Bug
        9. Functions should not be defined with a variable number of arguments

           Code Smell
        10. The right-hand operands of && and || should not contain side effects

           Code Smell
        11. Increment (++) and decrement (--) operators should not be used in a method call or mixed with other operators in an expression

           Code Smell
        12. Bitwise operators should not be applied to signed operands

           Bug
        13. Boolean operations should not have numeric operands, and vice versa

           Bug
        14. Limited dependence should be placed on operator precedence

           Code Smell
        15. Objects with integer type should not be converted to objects with pointer type

           Bug
        16. A cast shall not remove any const or volatile qualification from the type of a pointer or reference

           Code Smell
        17. Signed and unsigned types should not be mixed in expressions

           Code Smell
        18. Array declarations should include an explicit size specification

           Code Smell
        19. Literal suffix "L" for long integers shall be upper case

           Code Smell
        20. String literals with different prefixes should not be concatenated

           Bug
        21. Bit fields should be declared with appropriate types

           Code Smell
        22. Appropriate char types should be used for character and integer values

           Code Smell
        23. Identifiers should not be longer than 31 characters

           Code Smell
        24. Trigraphs should not be used

           Code Smell
        25. All uses of the #pragma directive should be documented

           Code Smell
        26. Names of well-known C standard library macros and functions should not be used as identifiers

           Code Smell
        27. Hard-coded secrets are security-sensitive

           Security Hotspot
        28. "sprintf" should not be used

           Security Hotspot
        29. Accessing files should not introduce TOCTOU vulnerabilities

           Vulnerability
        30. Macros should not be used as replacements for "typedef" and "using"

           Code Smell
        31. Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

           Security Hotspot
        32. Using "strncpy" or "wcsncpy" is security-sensitive

           Security Hotspot
        33. Using "strncat" or "wcsncat" is security-sensitive

           Security Hotspot
        34. Using "strcat" or "wcscat" is security-sensitive

           Security Hotspot
        35. Using "strlen" or "wcslen" is security-sensitive

           Security Hotspot
        36. Using "strcpy" or "wcscpy" is security-sensitive

           Security Hotspot
        37. POSIX functions should not be called with arguments that trigger buffer overflows

           Vulnerability
        38. Relational and subtraction operators should not be used with pointers to different arrays

           Bug
        39. Cipher algorithms should be robust

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

           Vulnerability
        41. Moved-from objects should not be relied upon

           Code Smell
        42. User-defined types should not be passed as variadic arguments

           Bug
        43. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        44. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        45. Integral operations should not overflow

           Bug
        46. Reference types should not be qualified with "const" or "volatile"

           Code Smell
        47. Local variables should not be volatile

           Code Smell
        48. Classes should have regular copy and move semantic

           Code Smell
        49. Closed resources should not be accessed

           Bug
        50. Dynamically allocated memory should be released

           Bug
        51. Freed memory should not be used

           Bug
        52. Memory access should be explicitly bounded to prevent buffer overflows

           Bug
        53. Zero should not be a possible denominator

           Bug
        54. Standard namespaces should not be modified

           Code Smell
        55. Function declarations that look like variable declarations should not be used

           Bug
        56. Format strings should be used correctly

           Code Smell
        57. Members should be initialized in the order they are declared

           Code Smell
        58. "sizeof" should not be called on pointers

           Bug
        59. Declarations should not be empty

           Code Smell
        60. Multiline blocks should be enclosed in curly braces

           Code Smell
        61. "nonnull" parameters and return values of "returns_nonnull" functions should not be null

           Bug
        62. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        63. Conditionally executed code should be reachable

           Bug
        64. Printf-style format strings should not lead to unexpected behavior at runtime

           Bug
        65. Null pointers should not be dereferenced

           Bug
        66. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        67. "for" loop counters should not have essentially floating type

           Bug
        68. Resources should be closed

           Bug
        69. Hard-coded passwords are security-sensitive

           Security Hotspot
        70. Comment styles "//" and "/* ... */" should not be mixed within a file

           Code Smell
        71. Obsolete POSIX functions should not be used

           Code Smell
        72. Code annotated as deprecated should not be used

           Code Smell
        73. Related "if/else if" statements should not have the same condition

           Bug
        74. Unused assignments should be removed

           Code Smell
        75. Pointers should not be cast to integral types

           Bug
        76. Identical expressions should not be used on both sides of a binary operator

           Bug
        77. All code should be reachable

           Bug
        78. "#pragma warning (default: ...)" should not be used

           Code Smell
        79. Virtual functions should not be called from constructors or destructors

           Code Smell
        80. Multiple variables should not be declared on the same line

           Code Smell
        81. Variables should not be self-assigned

           Bug
        82. File names should comply with a naming convention

           Code Smell
        83. Octal values should not be used

           Code Smell
        84. Using hardcoded IP addresses is security-sensitive

           Security Hotspot
        85. "switch" statements should have "default" clauses

           Code Smell
        86. Switch cases should end with an unconditional "break" statement

           Code Smell
        87. "operator delete" should be written along with "operator new"

           Bug
        88. "if ... else if" constructs should end with "else" clauses

           Code Smell
        89. Polymorphic base class destructor should be either public virtual or protected non-virtual

           Code Smell
        90. Appropriate memory de-allocation should be used

           Bug
        91. Control structures should use curly braces

           Code Smell
        92. Generic exceptions should not be caught

           Code Smell
        93. Unused function parameters should be removed

           Code Smell
        94. Assignments should not be made from within conditions

           Code Smell
        95. Generic exceptions should never be thrown

           Code Smell
        96. Variables should not be shadowed

           Code Smell
        97. Empty statements should be removed

           Code Smell
        98. "/*" and "//" should not be used within comments

           Code Smell
        99. Insecure functions should not be used

           Vulnerability
        100. Unused labels should be removed

           Code Smell
        101. Standard outputs should not be used directly to log anything

           Code Smell
        102. Handlers in a single try-catch or function-try-block for a derived class and some or all of its bases should be ordered most-derived-first

           Bug
        103. Exception classes should be caught by reference

           Bug
        104. Handlers of a function-try-block implementation of a class constructor or destructor shall not reference non-static members from this class or its bases

           Bug
        105. Control should not be transferred into a complex logic block using a "goto" or a "switch" statement

           Code Smell
        106. Header files should not contain unnamed namespaces

           Code Smell
        107. A function with non-"void" return type shall return a value on all paths

           Bug
        108. The built-in relational operators ">", ">=", "<" and "<=" shall not be applied to objects of pointer type, except where they point to elements of the same array

           Bug
        109. Subtraction between pointers shall only be applied to pointers that address elements of the same array

           Bug
        110. A value should not be "unnecessarily written" to a local object

           Code Smell

        Identifiers should not be longer than 31 characters

        consistency - identifiable
        maintainability
        Code Smell
        • based-on-misra
        • cert

        Why is this an issue?

        More Info

        In addition to being difficult to use, too-long variable names can limit code portability. The ISO standard requires that variable, type, function and label names be no more than 31 characters long.

        Note that 31 characters is an upper bound, rather than a length recommendation. Shorter names are better, as long as they’re still communicative.

        Noncompliant code example

        int this_is_a_very_long_identifier_that_definitely_should_be_renamed = 0;
        

        Compliant solution

        int reasonable_identifier = 0;
        
          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

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use