| title | description | ms.date | ms.topic | f1_keywords | helpviewer_keywords | author | ms.author | manager | ms.subservice | monikerRange | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CA2106: Secure asserts |
A method asserts a permission and performs no security checks on the caller. |
11/04/2016 |
reference |
|
|
mikejo5000 |
mikejo |
mijacobs |
code-analysis |
vs-2019 |
| Item | Value |
|---|---|
| RuleId | CA2106 |
| Category | Microsoft.Security |
| Breaking change | Breaking |
A method asserts a permission and performs no security checks on the caller.
Note
This rule has been deprecated. For more information, see Deprecated rules.
Asserting a security permission without performing any security checks can leave an exploitable security weakness in your code. A security stack walk stops when a security permission is asserted. If you assert a permission without performing any checks on the caller, the caller could indirectly execute code by using your permissions. Asserts without security checks are permissible if you're sure the assert can't be used in a harmful manner. An assert is harmless if the code you call is harmless, or if users can't pass arbitrary information to code that you call.
To fix a violation of this rule, add a security demand to the method or its declaring type.
Suppress a warning from this rule only after a careful security review.
- xref:System.Security.CodeAccessPermission.Assert%2A?displayProperty=fullName
- Secure Coding Guidelines