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)

Chapter 10: Using Components with Known Vulnerabilities

ASP.NET Core web developers rely on third-party commercial and open source frameworks, libraries, and packages to build web applications. This approach speeds up development time to support the rapid pace of business needs. While this saves developers a lot of time, there is a risk associated with using externally developed components. Code security in these libraries is often not guaranteed and, as with any other software, there will be security flaws. Software composition analysis (SCA) is necessary to find out whether your ASP.NET Core web application is using outdated and vulnerable packages.

In this chapter, we're going to cover the following recipes:

  • Fixing the use of a vulnerable third-party JavaScript library
  • Fixing the use of a vulnerable NuGet package
  • Fixing the use of a library hosted from an untrusted source

By the end of this chapter, you will have learned how to use browser add-ons...