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 674
  • Vulnerability13
  • Bug139
  • Security Hotspot19
  • Code Smell503

  • Quick Fix 91
Filtered: 62 rules found
cwe
    Impact
      Clean code attribute
        1. Function-like macros should not be invoked without all of their arguments

           Bug
        2. Function exit paths should have appropriate return values

           Bug
        3. Non-empty statements should change control flow or have at least one side-effect

           Bug
        4. Bitwise operators should not be applied to signed operands

           Bug
        5. Limited dependence should be placed on operator precedence

           Code Smell
        6. Variables should be initialized before use

           Bug
        7. Hard-coded secrets are security-sensitive

           Security Hotspot
        8. "sprintf" should not be used

           Security Hotspot
        9. Changing working directories without verifying the success is security-sensitive

           Security Hotspot
        10. Setting capabilities is security-sensitive

           Security Hotspot
        11. Accessing files should not introduce TOCTOU vulnerabilities

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

           Vulnerability
        13. Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

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

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

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

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

           Security Hotspot
        18. Changing directories improperly when using "chroot" is security-sensitive

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

           Security Hotspot
        20. "memset" should not be used to delete sensitive data

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

           Vulnerability
        22. Cipher algorithms should be robust

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

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

           Vulnerability
        25. "pthread_mutex_t" should not be locked when already locked, or unlocked when already unlocked

           Bug
        26. Using publicly writable directories is security-sensitive

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

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

           Code Smell
        29. Expanding archive files without controlling resource consumption is security-sensitive

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

           Vulnerability
        31. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        32. Cryptographic keys should be robust

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

           Vulnerability
        34. Dynamically allocated memory should be released

           Bug
        35. Freed memory should not be used

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

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

           Bug
        38. Zero should not be a possible denominator

           Bug
        39. "sizeof" should not be called on pointers

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

           Vulnerability
        41. Multiline blocks should be enclosed in curly braces

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

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

           Security Hotspot
        44. Conditionally executed code should be reachable

           Bug
        45. Exceptions should not be ignored

           Code Smell
        46. Null pointers should not be dereferenced

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

           Security Hotspot
        48. Resources should be closed

           Bug
        49. Hard-coded passwords are security-sensitive

           Security Hotspot
        50. Code annotated as deprecated should not be used

           Code Smell
        51. Unused assignments should be removed

           Code Smell
        52. All code should be reachable

           Bug
        53. "switch" statements should have "default" clauses

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

           Code Smell
        55. Generic exceptions should not be caught

           Code Smell
        56. Track uses of "TODO" tags

           Code Smell
        57. Track uses of "FIXME" tags

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

           Code Smell
        59. Generic exceptions should never be thrown

           Code Smell
        60. Insecure functions should not be used

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

           Vulnerability
        62. The value of an object must not be read before it has been set

           Bug

        Freed memory should not be used

        intentionality - logical
        reliability
        Bug
        • cwe
        • symbolic-execution
        • cert

        Accessing a memory block that was already freed is undefined behavior. This rule flags access via a pointer or a reference to released heap memory.

        Why is this an issue?

        How can I fix it?

        More Info

        A program may allocate an additional memory block using the malloc function. When no longer needed, such memory blocks are released using the free function. After it is released, reading or writing to a heap-allocated memory block leads to undefined behavior.

        char *cp = (char*)malloc(sizeof(char)*10); // memory is allocated
        // all bytes in cp can be used here
        free(cp); // memory is released
        cp[9] = 0; // Noncompliant: memory is used after it was released
        

        In addition to the malloc and free pair, in C++ a heap memory may be acquired by use of the operator new, and later released using the operator delete.

        int *intArray = new int[20]; // memory is allocated
        // elements of intArray can be written or read here
        delete[] intArray; // memory is released
        intArray[3] = 10; // Noncompliant: memory is used after it was released
        

        Releasing a memory block by invoking free or operator delete informs the memory management system that the program no longer uses the given block. Depending on the state and load of the program, such block can be then:

        • reused, i.e., the allocation function returns the same pointer,
        • released to the operating system, making it inaccessible to the program.

        What is the potential impact?

        Accessing released memory causes undefined behavior. This means the compiler is not bound by the language standard anymore, and your program has no meaning assigned to it.

        Practically this has a wide range of effects:

        • The program may crash due to the memory no longer being accessible, or due to unexpected value being read or written via the pointer.
        • Reading from the released memory may produce a garbage value.
        • When the memory was already reused to store sensitive data, such as passwords, it may lead to a vulnerability that uses this defect to extract information from an instance of the program.
        • Writing to released memory may change the value of the unrelated object in a remote part of the code if the memory was reused by it. As different objects may reuse same the block of memory between runs, this leads to unintuitive and hard diagnose bugs.
          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