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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more