ROSLYN.SECURITY.CA5391 : Use antiforgery tokens in ASP.NET Core MVC controllers (C#)

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

CodeSonar^® 9.2p0

CONFIDENTIAL

CodeSecure Inc

ROSLYN.SECURITY.CA5391 : Use antiforgery tokens in ASP.NET Core MVC controllers (C#)

Summary

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.

This check corresponds to Roslyn rule CA5391. For full rule details, see the Microsoft website: CA5391.

Properties

Class Name	Use antiforgery tokens in ASP.NET Core MVC controllers (C#)
Significance	security
Mnemonic	ROSLYN.SECURITY.CA5391
Categories	None
Availability	Available for C# only.
Enabling	Checks for this warning class are disabled by default. To enable them, add the following WARNING_FILTER rule to the project configuration file. WARNING_FILTER += allow class="Use antiforgery tokens in ASP.NET Core MVC controllers (C#)"

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.