Skip to main content

Inappropriate coding practices - Transparency Conflict

Description#

The application uses Transparency attributes such as SecurityCriticalAttribute and SecuritySafeCriticalAttribute to identify code that performs critical security operations. However a trasparency conflict is created when a member is marked with a security attribute that has a different transparency than the security attribute of a container of the member.

Impact#

Cause unexpected behaviors in the application

Recommendation#

Remove nested transparency annotation to avoid security attributes conflicts

Threat#

Anonymous attacker from Internet.

Score#

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base#

  • Attack vector: N
  • Attack complexity: H
  • Privileges required: N
  • User interaction: N
  • Scope: U
  • Confidentiality: N
  • Integrity: L
  • Availability: N

Temporal#

  • Exploit code madurity: U
  • Remediation level: U
  • Report confidence: R

Result#

  • Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:U/RC:R
  • Score:
    • Base: 3.7
    • Temporal: 3.3
  • Severity:
    • Base: Low
    • Temporal: Low

Details#

https://rules.sonarsource.com/csharp/type/Vulnerability/RSPEC-4211

Requirements#