VariantIncomplete

CWE-520.NET Misconfiguration: Use of Impersonation

Category: config

Description

Allowing a .NET application to run at potentially escalated levels of access to the underlying operating and file systems can be dangerous and result in various forms of attacks. .NET server applications can optionally execute using the identity of the user authenticated to the client. The intention of this functionality is to bypass authentication and access control checks within the .NET application code. Authentication is done by the underlying web server (Microsoft Internet Information Service IIS), which passes the authenticated token, or unauthenticated anonymous token, to the .NET application. Using the token to impersonate the client, the application then relies on the settings within the NTFS directories and files to control access. Impersonation enables the application, on the server running the .NET application, to both execute code and access resources in the context of the authenticated and authorized user.

Common consequences· 1

  • Access Control — Gain Privileges or Assume Identity

Potential mitigations· 1

  • [Operation]Run the application with limited privilege to the underlying operating and file system.

References

  1. https://cwe.mitre.org/data/definitions/520.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
ASP.NET Misconfiguration: Use of Identity Impersonation
CWE
ASP.NET Misconfiguration: Password in Configuration File
CWE
ASP.NET Misconfiguration: Missing Custom Error Page
CVE
Microsoft .NET Framework Remote Code Execution Vulnerability
CWE
ASP.NET Misconfiguration: Not Using Input Validation Framework
CWE
ASP.NET Misconfiguration: Creating Debug Binary
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.