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: 54 rules found
symbolic-execution
    Impact
      Clean code attribute
        1. 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
        2. Variables should be initialized before use

           Bug
        3. Variables should not be accessed outside of their scope

           Bug
        4. Well-defined type-punning method should be used instead of a union-based one

           Bug
        5. "std::cmp_*" functions should be used to compare unsigned values with negative values

           Bug
        6. "std::cmp_*" functions should be used to compare signed and unsigned values

           Code Smell
        7. Account validity should be verified when authenticating users with PAM

           Vulnerability
        8. Changing directories improperly when using "chroot" is security-sensitive

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

           Vulnerability
        10. Immediately dangling references and pointers should not be created

           Bug
        11. Server hostnames should be verified during SSL/TLS connections

           Vulnerability
        12. "pthread_mutex_t" should be unlocked in the reverse order they were locked

           Bug
        13. Only valid arguments should be passed to UNIX/POSIX functions

           Code Smell
        14. "pthread_mutex_t" should be properly initialized and destroyed

           Bug
        15. "pthread_mutex_t" should not be locked when already locked, or unlocked when already unlocked

           Bug
        16. Only valid arguments should be passed to stream functions

           Code Smell
        17. Using publicly writable directories is security-sensitive

           Security Hotspot
        18. Using clear-text protocols is security-sensitive

           Security Hotspot
        19. Blocking functions should not be called inside critical sections

           Code Smell
        20. Return value of "setuid" family of functions should always be checked

           Code Smell
        21. Size of variable length arrays should be greater than zero

           Code Smell
        22. "mktemp" family of functions templates should have at least six trailing "X"s

           Code Smell
        23. Appropriate size arguments should be passed to "strncat" and "strlcpy"

           Code Smell
        24. Moved-from objects should not be relied upon

           Code Smell
        25. Server certificates should be verified during SSL/TLS connections

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

           Vulnerability
        27. Integral operations should not overflow

           Bug
        28. Parameter values should be appropriate

           Bug
        29. Stack allocated memory and non-owned memory should not be freed

           Bug
        30. Closed resources should not be accessed

           Bug
        31. Dynamically allocated memory should be released

           Bug
        32. Freed memory should not be used

           Bug
        33. Memory locations should not be released more than once

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

           Bug
        35. Zero should not be a possible denominator

           Bug
        36. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        37. "nonnull" parameters and return values of "returns_nonnull" functions should not be null

           Bug
        38. Null pointers should not be dereferenced

           Bug
        39. Member variables should be initialized

           Bug
        40. Resources should be closed

           Bug
        41. Unused assignments should be removed

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

           Bug
        43. "Predicates" shall not have "persistent side effects"

           Bug
        44. An object shall not be accessed outside of its lifetime

           Bug
        45. Reads and writes on the same file stream shall be separated by a positioning operation

           Bug
        46. The pointer returned by the C++ Standard Library functions "asctime", "ctime", "gmtime", "localtime", "localeconv", "getenv", "setlocale" or "strerror" must not be used following a subsequent call to the same function

           Bug
        47. The value of an object must not be read before it has been set

           Bug
        48. The right-hand operand of a logical "&&" or "||" operator should not contain "persistent side effects"

           Bug
        49. 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
        50. Subtraction between pointers shall only be applied to pointers that address elements of the same array

           Bug
        51. Pointer arithmetic shall not form an invalid pointer

           Bug
        52. An object or subobject must not be copied to an overlapping object

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

           Code Smell
        54. Controlling expressions should not be invariant

           Bug

        An object or subobject must not be copied to an overlapping object

        intentionality - logical
        reliability
        Bug
        • symbolic-execution
        • unpredictable
        • misra-c++2023
        • misra-mandatory

        Why is this an issue?

        This rule is part of MISRA C++:2023.

        Usage of this content is governed by Sonar’s terms and conditions. Redistribution is prohibited.

        Rule 8.18.1 - An object or subobject must not be copied to an overlapping object

        [expr.ass] Undefined 8

        Category: Mandatory

        Analysis: Undecidable,System

        Amplification

        This rule applies when:

        • A member of a union is copied to a different member of the same union; or
        • A slice of an array is copied to an overlapping slice of the same array using memcpy.

        Rationale

        Copying between members of the same union object may result in undefined behaviour.

        If part of an array is to be copied to another part of the same array (e.g. when moving elements 1 to 10 to elements 0 to 9), then std::memcpy may overwrite an element before it has been copied, as there is no guarantee of the order in which they are copied. By contrast, std::memmove is guaranteed to handle the overlap appropriately.

        Example

        The use of unions in the following example is a violation of M23_158: MISRA C++ 2023 Rule 12.3.1.

        void f1( void )
        {
          union
          {
            int16_t i;
            int32_t j;
          } a = { 0 };
        
          a.i = a.i;         // Rule does not apply - same member
          a.j = a.i;         // Non-compliant
        }
        
        void f2( std::array< int16_t, 20 > & a )
        {
          memcpy ( &a[ 0 ], &a[ 1 ], 10u * sizeof ( a[ 0 ] ) );  // Non-compliant
          memmove( &a[ 0 ], &a[ 1 ], 10u * sizeof ( a[ 0 ] ) );  // Rule does not apply
          memcpy ( &a[ 1 ], &a[ 0 ], 10u * sizeof ( a[ 0 ] ) );  // Non-compliant
          memmove( &a[ 1 ], &a[ 0 ], 10u * sizeof ( a[ 0 ] ) );  // Rule does not apply
          memcpy ( &a[ 0 ], &a[ 5 ],  5u * sizeof ( a[ 0 ] ) );  // Compliant - no overlap
        }
        

        Copyright The MISRA Consortium Limited © 2023

          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

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use