Skip to main content

XML External Entity Attack and .NET Core

Improving the security of the systems I help design and build for my clients is a continuous effort where every day new vulnerabilities are discovered. That being said, the OWASP Top 10 hasn't change that much since it's original introduction.

This means that using the OWASP Top 10 remains a good starting point and the first important step towards more secure code.

During a security audit, we identified that one of our older (.NET) applications had an XML External Entities(XXE) vulnerability.

What is the XXE vulnerability?

An XML eXternal Entity injection (XXE) is an attack against applications that parse XML input. An XXE attack can happen when untrusted XML input with a reference to an external entity is processed by a weakly configured XML parser.

It is a high risk vulnerability as it can lead to:

  • A denial of service attack on the system
  • A Server Side Request Forgery (SSRF) attack
  • The ability to scan ports from the machine where the parser is located

One of the things that can be done through this attack is to retrieve files from the server. For example, if your application is using ASP.NET (Core) and running in IIS you probably have a web.config and maybe an appsettings.json file. By referring to this file as an external entity in the provided XML, the content can be read and returned in the response.

More information: payloadbox/xxe-injection-payload-list: XML External Entity (XXE) Injection Payload List (github.com)

How can we safeguard against this vulnerability in .NET (Core)?

The question is then how can we prevent this attack from happening. The good news is that if you are using a .NET Framework version ≥4.5.2, you are protected against this type of attack by default. Also .NET Core gives you protection against this out-of-the-box.

For this older ASP.NET application, we fixed the problem by updating the the <httpRuntime targetFramework="..." /> setting in the Web.config. Although the application was compiled against .NET 4.6 and the .NET 4.8 runtime was installed, it is not sufficient. The used .NET Framework Version for an ASP.NET applications is either the .NET version the application was build with or the httpRuntime's targetFramework (Web.config), whichever is lower(!).

If you cannot change the .NET version, it is recommended to explicitly disable external entity support for the xml parser:

More information

XML External Entity Prevention - OWASP Cheat Sheet Series

XML Denial of Service Attacks and Defenses | Microsoft Learn

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more