Book Image

ASP.NET Core 5 Secure Coding Cookbook

By : Roman Canlas
Book Image

ASP.NET Core 5 Secure Coding Cookbook

By: Roman Canlas

Overview of this book

ASP.NET Core developers are often presented with security test results showing the vulnerabilities found in their web apps. While the report may provide some high-level fix suggestions, it does not specify the exact steps that you need to take to resolve or fix weaknesses discovered by these tests. In ASP.NET Secure Coding Cookbook, you’ll start by learning the fundamental concepts of secure coding and then gradually progress to identifying common web app vulnerabilities in code. As you progress, you’ll cover recipes for fixing security misconfigurations in ASP.NET Core web apps. The book further demonstrates how you can resolve different types of Cross-Site Scripting. A dedicated section also takes you through fixing miscellaneous vulnerabilities that are no longer in the OWASP Top 10 list. This book features a recipe-style format, with each recipe containing sample unsecure code that presents the problem and corresponding solutions to eliminate the security bug. You’ll be able to follow along with each step of the exercise and use the accompanying sample ASP.NET Core solution to practice writing secure code. By the end of this book, you’ll be able to identify unsecure code causing different security flaws in ASP.NET Core web apps and you’ll have gained hands-on experience in removing vulnerabilities and security defects from your code.
Table of Contents (15 chapters)

Preventing Server-Side Request Forgery

ASP.NET Core web applications are composed of different layers and components to make it a whole working system. Most of the time, it requires a backend service that will either process or provide data to the base web application. These disparate services interconnect to form a cohesive and functioning web application. This is either done in the form of a web service or a REST-based API hosted internally or externally from the system, and our code then calls the operations of these APIs and web services (or microservices).

However, without proper filtering or being able to validate the data that's been sent to these services, the host could start executing unexpected actions. This vulnerability is otherwise known as Server-Side Request Forgery (SSRF), with adversaries exploiting the lack of validation or sanitization available.

Getting ready

Run the sample app to verify that there are no build or compile errors. In your command...