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 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
Filtered: 2 rules found
serialization
    Impact
      Clean code attribute
        1. Serialization constructors should be secured

           Vulnerability
        2. Deserialization methods should be provided for "OptionalField" members

           Bug

        Serialization constructors should be secured

        intentionality - complete
        security
        Vulnerability
        • serialization

        This rule is deprecated, and will eventually be removed.

        Why is this an issue?

        More Info

        Because serialization constructors allocate and initialize objects, security checks that are present on regular constructors must also be present on a serialization constructor. Failure to do so would allow callers that could not otherwise create an instance to use the serialization constructor to do this.

        This rule raises an issue when a type implements the System.Runtime.Serialization.ISerializable interface, is not a delegate or interface, is declared in an assembly that allows partially trusted callers and has a constructor that takes a System.Runtime.Serialization.SerializationInfo object and a System.Runtime.Serialization.StreamingContext object which is not secured by a security check, but one or more of the regular constructors in the type is secured.

        Noncompliant code example

        using System;
        using System.IO;
        using System.Runtime.Serialization;
        using System.Runtime.Serialization.Formatters.Binary;
        using System.Security;
        using System.Security.Permissions;
        
        [assembly: AllowPartiallyTrustedCallersAttribute()]
        namespace MyLibrary
        {
            [Serializable]
            public class Foo : ISerializable
            {
                private int n;
        
                [FileIOPermissionAttribute(SecurityAction.Demand, Unrestricted = true)]
                public Foo()
                {
                   n = -1;
                }
        
                protected Foo(SerializationInfo info, StreamingContext context) // Noncompliant
                {
                   n = (int)info.GetValue("n", typeof(int));
                }
        
                void ISerializable.GetObjectData(SerializationInfo info, StreamingContext context)
                {
                   info.AddValue("n", n);
                }
            }
        }
        

        Compliant solution

        using System;
        using System.IO;
        using System.Runtime.Serialization;
        using System.Runtime.Serialization.Formatters.Binary;
        using System.Security;
        using System.Security.Permissions;
        
        [assembly: AllowPartiallyTrustedCallersAttribute()]
        namespace MyLibrary
        {
            [Serializable]
            public class Foo : ISerializable
            {
                private int n;
        
                [FileIOPermissionAttribute(SecurityAction.Demand, Unrestricted = true)]
                public Foo()
                {
                   n = -1;
                }
        
                [FileIOPermissionAttribute(SecurityAction.Demand, Unrestricted = true)]
                protected Foo(SerializationInfo info, StreamingContext context)
                {
                   n = (int)info.GetValue("n", typeof(int));
                }
        
                void ISerializable.GetObjectData(SerializationInfo info, StreamingContext context)
                {
                   info.AddValue("n", n);
                }
            }
        }
        
          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 Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • 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