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 log injection

In Chapter 11, Insufficient Logging and Monitoring, we learned about the importance of logging. Logging provides us with the necessary visibility to find out about a series of important events in our ASP.NET Core web application. However, hackers can also exploit logging if the user-controlled log information we create is not validated. Having malicious inputs in our log entries can also exploit the vulnerabilities of a log viewer, if one exists.

For instance, a web-based log viewer might have a cross-site script vulnerability, and viewing the log entries with an XSS payload, along with the data, can exploit this weakness. In this recipe, we will prevent the log injection vulnerability in our code by implementing input sanitization.

Getting ready

Run the sample app to verify that there are no build or compile errors. In your command shell, navigate to the sample app folder at \Chapter12\log-injection\before\OnlineBankingApp and run the following command...