Reducing Third-Party Security Risk in .NET Core Applications
summary
Shows a demo MVC app where an included PDF component allows path traversal and server‑side request forgery (loads remote images). Uses .NET Core 3.1 AssemblyLoadContext plus a self‑contained deployment to load the PDF library in an isolated context, replaces System.Net.Http with a stub to block external fetches while still permitting local files, and proves the sandbox works. Ships a CLI called fennec (Mono.Cecil) to dump API calls for review. Cites Veracode stats: ~85% → ~70% vulnerable apps.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:46Reducing Third-Party Security Risk in .NET Core Applications
- 5:20Third-Party Security Risks
- 7:30State of Software Security
- 11:50Octopus Scanner
- 13:33Supply Chain Attacks
- 14:40ASUS Live Update
- 29:03Compartmentalization of functionality
- 29:50System.AppDomain
- 31:56System.Runtime.Loader.Assembly LoadContext
- 49:29Changes in Software Architecture
- 50:27Review Third-Party Libraries
- 56:39Microsoft Application Inspector
- 57:27Conclusion
related talks
49mReducing Third-Party Security Risk in .NET Core Applications
58mReducing Third-Party Security Risk in .NET Core Applications
01h 03mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
58mASP.NET Core meets OWASP Top 10 2025
52mBuilding Community-Driven Security Analysis for Your .NET Software Supply Chain
52mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
54mASP.NET Core Meets Owasp Top 10
32mBuilding Secure ASP.NET Core MVC Applications
