| 1 |
CA1303 |
Do not pass literals as localized parameters |
Globalization |
True |
False |
A method passes a string literal as a parameter to a constructor or method in the .NET Framework class library and that string should be localizable. To fix a violation of this rule, replace the string literal with a string retrieved through an instance of the ResourceManager class. |
| 2 |
CA1304 |
Specify CultureInfo |
Globalization |
True |
True |
A method or constructor calls a member that has an overload that accepts a System.Globalization.CultureInfo parameter, and the method or constructor does not call the overload that takes the CultureInfo parameter. When a CultureInfo or System.IFormatProvider object is not supplied, the default value that is supplied by the overloaded member might not have the effect that you want in all locales. If the result will be displayed to the user, specify 'CultureInfo.CurrentCulture' as the 'CultureInfo' parameter. Otherwise, if the result will be stored and accessed by software, such as when it is persisted to disk or to a database, specify 'CultureInfo.InvariantCulture'. |
| 3 |
CA1305 |
Specify IFormatProvider |
Globalization |
True |
True |
A method or constructor calls one or more members that have overloads that accept a System.IFormatProvider parameter, and the method or constructor does not call the overload that takes the IFormatProvider parameter. When a System.Globalization.CultureInfo or IFormatProvider object is not supplied, the default value that is supplied by the overloaded member might not have the effect that you want in all locales. If the result will be based on the input from/output displayed to the user, specify 'CultureInfo.CurrentCulture' as the 'IFormatProvider'. Otherwise, if the result will be stored and accessed by software, such as when it is loaded from disk/database and when it is persisted to disk/database, specify 'CultureInfo.InvariantCulture' |
| 4 |
CA1307 |
Specify StringComparison |
Globalization |
True |
True |
A string comparison operation uses a method overload that does not set a StringComparison parameter. If the result will be displayed to the user, such as when sorting a list of items for display in a list box, specify 'StringComparison.CurrentCulture' or 'StringComparison.CurrentCultureIgnoreCase' as the 'StringComparison' parameter. If comparing case-insensitive identifiers, such as file paths, environment variables, or registry keys and values, specify 'StringComparison.OrdinalIgnoreCase'. Otherwise, if comparing case-sensitive identifiers, specify 'StringComparison.Ordinal'. |
| 5 |
CA1308 |
Normalize strings to uppercase |
Globalization |
True |
True |
Strings should be normalized to uppercase. A small group of characters cannot make a round trip when they are converted to lowercase. To make a round trip means to convert the characters from one locale to another locale that represents character data differently, and then to accurately retrieve the original characters from the converted characters. |
| 6 |
CA1309 |
Use ordinal stringcomparison |
Globalization |
False |
True |
A string comparison operation that is nonlinguistic does not set the StringComparison parameter to either Ordinal or OrdinalIgnoreCase. By explicitly setting the parameter to either StringComparison.Ordinal or StringComparison.OrdinalIgnoreCase, your code often gains speed, becomes more correct, and becomes more reliable. |
| 7 |
CA1401 |
P/Invokes should not be visible |
Interoperability |
True |
False |
A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. |
| 8 |
CA1810 |
Initialize reference type static fields inline |
Performance |
True |
True |
A reference type declares an explicit static constructor. To fix a violation of this rule, initialize all static data when it is declared and remove the static constructor. |
| 9 |
CA1813 |
Avoid unsealed attributes |
Performance |
False |
True |
The .NET Framework class library provides methods for retrieving custom attributes. By default, these methods search the attribute inheritance hierarchy. Sealing the attribute eliminates the search through the inheritance hierarchy and can improve performance. |
| 10 |
CA1816 |
Dispose methods should call SuppressFinalize |
Usage |
True |
True |
A method that is an implementation of Dispose does not call GC.SuppressFinalize; or a method that is not an implementation of Dispose calls GC.SuppressFinalize; or a method calls GC.SuppressFinalize and passes something other than this (Me in Visual?Basic). |
| 11 |
CA1820 |
Test for empty strings using string length |
Performance |
True |
True |
Comparing strings by using the String.Length property or the String.IsNullOrEmpty method is significantly faster than using Equals. |
| 12 |
CA1824 |
Mark assemblies with NeutralResourcesLanguageAttribute |
Performance |
True |
False |
The NeutralResourcesLanguage attribute informs the ResourceManager of the language that was used to display the resources of a neutral culture for an assembly. This improves lookup performance for the first resource that you load and can reduce your working set. |
| 13 |
CA1825 |
Avoid zero-length array allocations. |
Performance |
True |
True |
Avoid unnecessary zero-length array allocations. Use {0} instead. |
| 14 |
CA1826 |
Do not use Enumerable methods on indexable collections. Instead use the collection directly |
Performance |
True |
True |
This collection is directly indexable. Going through LINQ here causes unnecessary allocations and CPU work. |
| 15 |
CA1827 |
Do not use Count() or LongCount() when Any() can be used |
Performance |
True |
True |
For non-empty collections, Count() and LongCount() enumerate the entire sequence, while Any() stops at the first item or the first item that satisfies a condition. |
| 16 |
CA1828 |
Do not use CountAsync() or LongCountAsync() when AnyAsync() can be used |
Performance |
True |
True |
For non-empty collections, CountAsync() and LongCountAsync() enumerate the entire sequence, while AnyAsync() stops at the first item or the first item that satisfies a condition. |
| 17 |
CA1829 |
Use Length/Count property instead of Count() when available |
Performance |
True |
True |
Enumerable.Count() potentially enumerates the sequence while a Length/Count property is a direct access. |
| 18 |
CA2000 |
Dispose objects before losing scope |
Reliability |
True |
False |
If a disposable object is not explicitly disposed before all references to it are out of scope, the object will be disposed at some indeterminate time when the garbage collector runs the finalizer of the object. Because an exceptional event might occur that will prevent the finalizer of the object from running, the object should be explicitly disposed instead. |
| 19 |
CA2002 |
Do not lock on objects with weak identity |
Reliability |
True |
False |
An object is said to have a weak identity when it can be directly accessed across application domain boundaries. A thread that tries to acquire a lock on an object that has a weak identity can be blocked by a second thread in a different application domain that has a lock on the same object. |
| 20 |
CA2008 |
Do not create tasks without passing a TaskScheduler |
Reliability |
True |
True |
Do not create tasks unless you are using one of the overloads that takes a TaskScheduler. The default is to schedule on TaskScheduler.Current, which would lead to deadlocks. Either use TaskScheduler.Default to schedule on the thread pool, or explicitly pass TaskScheduler.Current to make your intentions clear. |
| 21 |
CA2009 |
Do not call ToImmutableCollection on an ImmutableCollection value |
Reliability |
True |
True |
Do not call {0} on an {1} value |
| 22 |
CA2010 |
Always consume the value returned by methods marked with PreserveSigAttribute |
Reliability |
True |
False |
PreserveSigAttribute indicates that a method will return an HRESULT, rather than throwing an exception. Therefore, it is important to consume the HRESULT returned by the method, so that errors can be detected. Generally, this is done by calling Marshal.ThrowExceptionForHR. |
| 23 |
CA2100 |
Review SQL queries for security vulnerabilities |
Security |
True |
False |
SQL queries that directly use user input can be vulnerable to SQL injection attacks. Review this SQL query for potential vulnerabilities, and consider using a parameterized SQL query. |
| 24 |
CA2101 |
Specify marshaling for P/Invoke string arguments |
Globalization |
True |
True |
A platform invoke member allows partially trusted callers, has a string parameter, and does not explicitly marshal the string. This can cause a potential security vulnerability. |
| 25 |
CA2201 |
Do not raise reserved exception types |
Usage |
False |
False |
An exception of type that is not sufficiently specific or reserved by the runtime should never be raised by user code. This makes the original error difficult to detect and debug. If this exception instance might be thrown, use a different exception type. |
| 26 |
CA2207 |
Initialize value type static fields inline |
Usage |
True |
True |
A value type declares an explicit static constructor. To fix a violation of this rule, initialize all static data when it is declared and remove the static constructor. |
| 27 |
CA2208 |
Instantiate argument exceptions correctly |
Usage |
True |
True |
A call is made to the default (parameterless) constructor of an exception type that is or derives from ArgumentException, or an incorrect string argument is passed to a parameterized constructor of an exception type that is or derives from ArgumentException. |
| 28 |
CA2213 |
Disposable fields should be disposed |
Usage |
True |
False |
A type that implements System.IDisposable declares fields that are of types that also implement IDisposable. The Dispose method of the field is not called by the Dispose method of the declaring type. To fix a violation of this rule, call Dispose on fields that are of types that implement IDisposable if you are responsible for allocating and releasing the unmanaged resources held by the field. |
| 29 |
CA2216 |
Disposable types should declare finalizer |
Usage |
True |
True |
A type that implements System.IDisposable and has fields that suggest the use of unmanaged resources does not implement a finalizer, as described by Object.Finalize. |
| 30 |
CA2229 |
Implement serialization constructors |
Usage |
True |
True |
To fix a violation of this rule, implement the serialization constructor. For a sealed class, make the constructor private; otherwise, make it protected. |
| 31 |
CA2235 |
Mark all non-serializable fields |
Usage |
True |
True |
An instance field of a type that is not serializable is declared in a type that is serializable. |
| 32 |
CA2237 |
Mark ISerializable types with serializable |
Usage |
True |
True |
To be recognized by the common language runtime as serializable, types must be marked by using the SerializableAttribute attribute even when the type uses a custom serialization routine through implementation of the ISerializable interface. |
| 33 |
CA2241 |
Provide correct arguments to formatting methods |
Usage |
True |
False |
The format argument that is passed to System.String.Format does not contain a format item that corresponds to each object argument, or vice versa. |
| 34 |
CA2242 |
Test for NaN correctly |
Usage |
True |
True |
This expression tests a value against Single.Nan or Double.Nan. Use Single.IsNan(Single) or Double.IsNan(Double) to test the value. |
| 35 |
CA2243 |
Attribute string literals should parse correctly |
Usage |
True |
False |
The string literal parameter of an attribute does not parse correctly for a URL, a GUID, or a version. |
| 36 |
CA2300 |
Do not use insecure deserializer BinaryFormatter |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data. If you need to instead detect BinaryFormatter deserialization without a SerializationBinder set, then disable rule CA2300, and enable rules CA2301 and CA2302. |
| 37 |
CA2301 |
Do not call BinaryFormatter.Deserialize without first setting BinaryFormatter.Binder |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data without a SerializationBinder to restrict the type of objects in the deserialized object graph. |
| 38 |
CA2302 |
Ensure BinaryFormatter.Binder is set before calling BinaryFormatter.Deserialize |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data without a SerializationBinder to restrict the type of objects in the deserialized object graph. |
| 39 |
CA2305 |
Do not use insecure deserializer LosFormatter |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data. |
| 40 |
CA2310 |
Do not use insecure deserializer NetDataContractSerializer |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data. If you need to instead detect NetDataContractSerializer deserialization without a SerializationBinder set, then disable rule CA2310, and enable rules CA2311 and CA2312. |
| 41 |
CA2311 |
Do not deserialize without first setting NetDataContractSerializer.Binder |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data without a SerializationBinder to restrict the type of objects in the deserialized object graph. |
| 42 |
CA2312 |
Ensure NetDataContractSerializer.Binder is set before deserializing |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data without a SerializationBinder to restrict the type of objects in the deserialized object graph. |
| 43 |
CA2315 |
Do not use insecure deserializer ObjectStateFormatter |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data. |
| 44 |
CA2321 |
Do not deserialize with JavaScriptSerializer using a SimpleTypeResolver |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data with a JavaScriptSerializer initialized with a SimpleTypeResolver. Initialize JavaScriptSerializer without a JavaScriptTypeResolver specified, or initialize with a JavaScriptTypeResolver that limits the types of objects in the deserialized object graph. |
| 45 |
CA2322 |
Ensure JavaScriptSerializer is not initialized with SimpleTypeResolver before deserializing |
Security |
False |
False |
The method '{0}' is insecure when deserializing untrusted data with a JavaScriptSerializer initialized with a SimpleTypeResolver. Ensure that the JavaScriptSerializer is initialized without a JavaScriptTypeResolver specified, or initialized with a JavaScriptTypeResolver that limits the types of objects in the deserialized object graph. |
| 46 |
CA2326 |
Do not use TypeNameHandling values other than None |
Security |
False |
False |
Deserializing JSON when using a TypeNameHandling value other than None can be insecure. If you need to instead detect Json.NET deserialization when a SerializationBinder isn't specified, then disable rule CA2326, and enable rules CA2327, CA2328, CA2329, and CA2330. |
| 47 |
CA2327 |
Do not use insecure JsonSerializerSettings |
Security |
False |
False |
When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using JsonSerializerSettings, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder. |
| 48 |
CA2328 |
Ensure that JsonSerializerSettings are secure |
Security |
False |
False |
When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using JsonSerializerSettings, ensure TypeNameHandling.None is specified, or for values other than None, ensure a SerializationBinder is specified to restrict deserialized types. |
| 49 |
CA2329 |
Do not deserialize with JsonSerializer using an insecure configuration |
Security |
False |
False |
When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using deserializing JsonSerializer, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder. |
| 50 |
CA2330 |
Ensure that JsonSerializer has a secure configuration when deserializing |
Security |
False |
False |
When deserializing untrusted input, allowing arbitrary types to be deserialized is insecure. When using deserializing JsonSerializer, use TypeNameHandling.None, or for values other than None, restrict deserialized types with a SerializationBinder. |
| 51 |
CA3001 |
Review code for SQL injection vulnerabilities |
Security |
False |
False |
Potential SQL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 52 |
CA3002 |
Review code for XSS vulnerabilities |
Security |
False |
False |
Potential cross-site scripting (XSS) vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 53 |
CA3003 |
Review code for file path injection vulnerabilities |
Security |
False |
False |
Potential file path injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 54 |
CA3004 |
Review code for information disclosure vulnerabilities |
Security |
False |
False |
Potential information disclosure vulnerability was found where '{0}' in method '{1}' may contain unintended information from '{2}' in method '{3}'. |
| 55 |
CA3005 |
Review code for LDAP injection vulnerabilities |
Security |
False |
False |
Potential LDAP injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 56 |
CA3006 |
Review code for process command injection vulnerabilities |
Security |
False |
False |
Potential process command injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 57 |
CA3007 |
Review code for open redirect vulnerabilities |
Security |
False |
False |
Potential open redirect vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 58 |
CA3008 |
Review code for XPath injection vulnerabilities |
Security |
False |
False |
Potential XPath injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 59 |
CA3009 |
Review code for XML injection vulnerabilities |
Security |
False |
False |
Potential XML injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 60 |
CA3010 |
Review code for XAML injection vulnerabilities |
Security |
False |
False |
Potential XAML injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 61 |
CA3011 |
Review code for DLL injection vulnerabilities |
Security |
False |
False |
Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 62 |
CA3012 |
Review code for regex injection vulnerabilities |
Security |
False |
False |
Potential regex injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. |
| 63 |
CA3061 |
Do Not Add Schema By URL |
Security |
True |
False |
This overload of XmlSchemaCollection.Add method internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. |
| 64 |
CA5350 |
Do Not Use Weak Cryptographic Algorithms |
Security |
True |
False |
Cryptographic algorithms degrade over time as attacks become for advances to attacker get access to more computation. Depending on the type and application of this cryptographic algorithm, further degradation of the cryptographic strength of it may allow attackers to read enciphered messages, tamper with enciphered messages, forge digital signatures, tamper with hashed content, or otherwise compromise any cryptosystem based on this algorithm. Replace encryption uses with the AES algorithm (AES-256, AES-192 and AES-128 are acceptable) with a key length greater than or equal to 128 bits. Replace hashing uses with a hashing function in the SHA-2 family, such as SHA-2 512, SHA-2 384, or SHA-2 256. |
| 65 |
CA5351 |
Do Not Use Broken Cryptographic Algorithms |
Security |
True |
False |
An attack making it computationally feasible to break this algorithm exists. This allows attackers to break the cryptographic guarantees it is designed to provide. Depending on the type and application of this cryptographic algorithm, this may allow attackers to read enciphered messages, tamper with enciphered messages, forge digital signatures, tamper with hashed content, or otherwise compromise any cryptosystem based on this algorithm. Replace encryption uses with the AES algorithm (AES-256, AES-192 and AES-128 are acceptable) with a key length greater than or equal to 128 bits. Replace hashing uses with a hashing function in the SHA-2 family, such as SHA512, SHA384, or SHA256. Replace digital signature uses with RSA with a key length greater than or equal to 2048-bits, or ECDSA with a key length greater than or equal to 256 bits. |
| 66 |
CA5358 |
Do Not Use Unsafe Cipher Modes |
Security |
False |
False |
These modes are vulnerable to attacks. Use only approved modes (CBC, CTS). |
| 67 |
CA5359 |
Do Not Disable Certificate Validation |
Security |
True |
False |
A certificate can help authenticate the identity of the server. Clients should validate the server certificate to ensure requests are sent to the intended server. If the ServerCertificateValidationCallback always returns 'true', any certificate will pass validation. |
| 68 |
CA5360 |
Do Not Call Dangerous Methods In Deserialization |
Security |
True |
False |
Insecure Deserialization is a vulnerability which occurs when untrusted data is used to abuse the logic of an application, inflict a Denial-of-Service (DoS) attack, or even execute arbitrary code upon it being deserialized. It’s frequently possible for malicious users to abuse these deserialization features when the application is deserializing untrusted data which is under their control. Specifically, invoke dangerous methods in the process of deserialization. Successful insecure deserialization attacks could allow an attacker to carry out attacks such as DoS attacks, authentication bypasses, and remote code execution. |
| 69 |
CA5361 |
Do Not Disable SChannel Use of Strong Crypto |
Security |
True |
False |
Starting with the .NET Framework 4.6, the System.Net.ServicePointManager and System.Net.Security.SslStream classes are recommeded to use new protocols. The old ones have protocol weaknesses and are not supported. Setting Switch.System.Net.DontEnableSchUseStrongCrypto with true will use the old weak crypto check and opt out of the protocol migration. |
| 70 |
CA5362 |
Do Not Refer Self In Serializable Class |
Security |
False |
False |
This can allow an attacker to DOS or exhaust the memory of the process. |
| 71 |
CA5363 |
Do Not Disable Request Validation |
Security |
True |
False |
Request validation is a feature in ASP.NET that examines HTTP requests and determines whether they contain potentially dangerous content. This check adds protection from markup or code in the URL query string, cookies, or posted form values that might have been added for malicious purposes. So, it is generally desirable and should be left enabled for defense in depth. |
| 72 |
CA5364 |
Do Not Use Deprecated Security Protocols |
Security |
True |
False |
Using a deprecated security protocol rather than the system default is risky. |
| 73 |
CA5365 |
Do Not Disable HTTP Header Checking |
Security |
True |
False |
HTTP header checking enables encoding of the carriage return and newline characters, \r and \n, that are found in response headers. This encoding can help to avoid injection attacks that exploit an application that echoes untrusted data contained by the header. |
| 74 |
CA5366 |
Use XmlReader For DataSet Read Xml |
Security |
True |
False |
Processing XML from untrusted data may load dangerous external references, which should be restricted by using an XmlReader with a secure resolver or with DTD processing disabled. |
| 75 |
CA5367 |
Do Not Serialize Types With Pointer Fields |
Security |
False |
False |
Pointers are not "type safe" in the sense that you cannot guarantee the correctness of the memory they point at. So, serializing types with pointer fields is dangerous, as it may allow an attacker to control the pointer. |
| 76 |
CA5368 |
Set ViewStateUserKey For Classes Derived From Page |
Security |
True |
False |
Setting the ViewStateUserKey property can help you prevent attacks on your application by allowing you to assign an identifier to the view-state variable for individual users so that they cannot use the variable to generate an attack. Otherwise, there will be cross-site request forgery vulnerabilities. |
| 77 |
CA5369 |
Use XmlReader For Deserialize |
Security |
True |
False |
Processing XML from untrusted data may load dangerous external references, which should be restricted by using an XmlReader with a secure resolver or with DTD processing disabled. |
| 78 |
CA5370 |
Use XmlReader For Validating Reader |
Security |
True |
False |
Processing XML from untrusted data may load dangerous external references, which should be restricted by using an XmlReader with a secure resolver or with DTD processing disabled. |
| 79 |
CA5371 |
Use XmlReader For Schema Read |
Security |
True |
False |
Processing XML from untrusted data may load dangerous external references, which should be restricted by using an XmlReader with a secure resolver or with DTD processing disabled. |
| 80 |
CA5372 |
Use XmlReader For XPathDocument |
Security |
True |
False |
Processing XML from untrusted data may load dangerous external references, which should be restricted by using an XmlReader with a secure resolver or with DTD processing disabled. |
| 81 |
CA5373 |
Do not use obsolete key derivation function |
Security |
True |
False |
Password-based key derivation should use PBKDF2 with SHA-2. Avoid using PasswordDeriveBytes since it generates a PBKDF1 key. Avoid using Rfc2898DeriveBytes.CryptDeriveKey since it doesn't use the iteration count or salt. |
| 82 |
CA5374 |
Do Not Use XslTransform |
Security |
True |
False |
Do not use XslTransform. It does not restrict potentially dangerous external references. |
| 83 |
CA5375 |
Do Not Use Account Shared Access Signature |
Security |
False |
False |
Shared Access Signatures(SAS) are a vital part of the security model for any application using Azure Storage, they should provide limited and safe permissions to your storage account to clients that don't have the account key. All of the operations available via a service SAS are also available via an account SAS, that is, account SAS is too powerful. So it is recommended to use Service SAS to delegate access more carefully. |
| 84 |
CA5376 |
Use SharedAccessProtocol HttpsOnly |
Security |
True |
False |
HTTPS encrypts network traffic. Use HttpsOnly, rather than HttpOrHttps, to ensure network traffic is always encrypted to help prevent disclosure of sensitive data. |
| 85 |
CA5377 |
Use Container Level Access Policy |
Security |
True |
False |
No access policy identifier is specified, making tokens non-revocable. |
| 86 |
CA5378 |
Do not disable ServicePointManagerSecurityProtocols |
Security |
True |
False |
Do not set Switch.System.ServiceModel.DisableUsingServicePointManagerSecurityProtocols to true. Setting this switch limits Windows Communication Framework (WCF) to using Transport Layer Security (TLS) 1.0, which is insecure and obsolete. |
| 87 |
CA5379 |
Do Not Use Weak Key Derivation Function Algorithm |
Security |
True |
False |
Some implementations of the Rfc2898DeriveBytes class allow for a hash algorithm to be specified in a constructor parameter or overwritten in the HashAlgorithm property. If a hash algorithm is specified, then it should be SHA-256 or higher. |
| 88 |
CA5380 |
Do Not Add Certificates To Root Store |
Security |
True |
False |
By default, the Trusted Root Certification Authorities certificate store is configured with a set of public CAs that has met the requirements of the Microsoft Root Certificate Program. Since all trusted root CAs can issue certificates for any domain, an attacker can pick a weak or coercible CA that you install by yourself to target for an attack – and a single vulnerable, malicious or coercible CA undermines the security of the entire system. To make matters worse, these attacks can go unnoticed quite easily. |
| 89 |
CA5381 |
Ensure Certificates Are Not Added To Root Store |
Security |
True |
False |
By default, the Trusted Root Certification Authorities certificate store is configured with a set of public CAs that has met the requirements of the Microsoft Root Certificate Program. Since all trusted root CAs can issue certificates for any domain, an attacker can pick a weak or coercible CA that you install by yourself to target for an attack – and a single vulnerable, malicious or coercible CA undermines the security of the entire system. To make matters worse, these attacks can go unnoticed quite easily. |
| 90 |
CA5382 |
Use Secure Cookies In ASP.Net Core |
Security |
False |
False |
Applications available over HTTPS must use secure cookies. |
| 91 |
CA5383 |
Ensure Use Secure Cookies In ASP.Net Core |
Security |
False |
False |
Applications available over HTTPS must use secure cookies. |
| 92 |
CA5384 |
Do Not Use Digital Signature Algorithm (DSA) |
Security |
True |
False |
DSA is too weak to use. |
| 93 |
CA5385 |
Use Rivest–Shamir–Adleman (RSA) Algorithm With Sufficient Key Size |
Security |
True |
False |
Encryption algorithms are vulnerable to brute force attacks when too small a key size is used. |
| 94 |
CA5386 |
Avoid hardcoding SecurityProtocolType value |
Security |
False |
False |
Avoid hardcoding SecurityProtocolType {0}, and instead use SecurityProtocolType.SystemDefault to allow the operating system to choose the best Transport Layer Security protocol to use. |
| 95 |
CA5387 |
Do Not Use Weak Key Derivation Function With Insufficient Iteration Count |
Security |
False |
False |
When deriving cryptographic keys from user-provided inputs such as password, use sufficient iteration count (at least 100k). |
| 96 |
CA5388 |
Ensure Sufficient Iteration Count When Using Weak Key Derivation Function |
Security |
False |
False |
When deriving cryptographic keys from user-provided inputs such as password, use sufficient iteration count (at least 100k). |
| 97 |
CA5389 |
Do Not Add Archive Item's Path To The Target File System Path |
Security |
True |
False |
When extracting files from an archive and using the archive item's path, check if the path is safe. Archive path can be relative and can lead to file system access outside of the expected file system target path, leading to malicious config changes and remote code execution via lay-and-wait technique. |
| 98 |
CA5390 |
Do Not Hard Code Encryption Key |
Security |
True |
False |
SymmetricAlgorithm's .Key property, or a method's rgbKey parameter, should never be a hardcoded value. |
| 99 |
CA5391 |
Use antiforgery tokens in ASP.NET Core MVC controllers |
Security |
True |
False |
Handling a POST, PUT, PATCH, or DELETE request without validating an antiforgery token may be vulnerable to cross-site request forgery attacks. A cross-site request forgery attack can send malicious requests from an authenticated user to your ASP.NET Core MVC controller. |
| 100 |
CA5392 |
Use DefaultDllImportSearchPaths attribute for P/Invokes |
Security |
True |
False |
By default, P/Invokes using DllImportAttribute probe a number of directories, including the current working directory for the library to load. This can be a security issue for certain applications, leading to DLL hijacking. |
| 101 |
CA5393 |
Do not use unsafe DllImportSearchPath value |
Security |
True |
False |
There could be a malicious DLL in the default DLL search directories. Or, depending on where your application is run from, there could be a malicious DLL in the application's directory. Use a DllImportSearchPath value that specifies an explicit search path instead. The DllImportSearchPath flags that this rule looks for can be configured in .editorconfig. |
| 102 |
CA5394 |
Do not use insecure randomness |
Security |
False |
False |
{0} is an insecure random number generator. Use cryptographically secure random number generators when randomness is required for security |
| 103 |
CA5395 |
Miss HttpVerb attribute for action methods |
Security |
False |
False |
All the methods that create, edit, delete, or otherwise modify data do so in the [HttpPost] overload of the method, which needs to be protected with the anti forgery attribute from request forgery. Performing a GET operation should be a safe operation that has no side effects and doesn't modify your persisted data. |
| 104 |
CA5396 |
Set HttpOnly to true for HttpCookie |
Security |
False |
False |
As a defense in depth measure, ensure security sensitive HTTP cookies are marked as HttpOnly. This indicates web browsers should disallow scripts from accessing the cookies. Injected malicious scripts are a common way of stealing cookies. |
| 105 |
CA5397 |
Do not use deprecated SslProtocols values |
Security |
True |
False |
Older protocol versions of Transport Layer Security (TLS) are less secure than TLS 1.2 and TLS 1.3, and are more likely to have new vulnerabilities. Avoid older protocol versions to minimize risk. |
| 106 |
CA5398 |
Avoid hardcoded SslProtocols values |
Security |
False |
False |
Current Transport Layer Security protocol versions may become deprecated if vulnerabilities are found. Avoid hardcoding SslProtocols values to keep your application secure. Use 'None' to let the Operating System choose a version. |