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: 5 rules found
denial-of-service
    Impact
      Clean code attribute
        1. Dynamically allocated memory should be released

           Bug
        2. Zero should not be a possible denominator

           Bug
        3. Resources should be closed

           Bug
        4. Polymorphic base class destructor should be either public virtual or protected non-virtual

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

           Bug

        Polymorphic base class destructor should be either public virtual or protected non-virtual

        intentionality - complete
        maintainability
        Code Smell
        • cppcoreguidelines
        • denial-of-service
        • cert

        Why is this an issue?

        More Info

        When a class with no virtual destructor is used as a base class, surprises can occur if pointers to instances of this class are used. Specifically, if an instance of a derived class is deleted through a pointer to the base type, the behavior is undefined and can lead to resource leaks, crashes or corrupted memory.

        If it is not expected for base class pointers to be deleted, then the destructor should be made protected to avoid such a misuse.

        Noncompliant code example

        class Base { // Noncompliant: no destructor is supplied, and the default version is not virtual
        public:
          Base() {}
          virtual void doSomething() {}
        };
        
        class Derived : public Base {
        }
        
        void f() {
          Base *p = new Derived();
          delete p; // Undefined behavior
        }
        

        Compliant solution

        class Base {
        public:
          Base() {}
          virtual ~Base() = default;
          virtual void doSomething() {}
        };
        
          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