CVE-2021-26423

7.5 HIGH

📋 TL;DR

CVE-2021-26423 is a denial-of-service vulnerability in .NET Core and Visual Studio where an attacker can cause the application to crash by sending specially crafted requests. This affects applications built with vulnerable .NET Core versions and developers using affected Visual Studio versions. The vulnerability requires the attacker to be able to send requests to the vulnerable application.

💻 Affected Systems

Products:
  • .NET Core
  • Visual Studio
Versions: .NET Core 5.0, 3.1, 2.1; Visual Studio 2019 version 16.9 and earlier
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: All .NET Core applications using affected versions are vulnerable regardless of configuration. Visual Studio vulnerability affects the development environment itself.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service unavailability for .NET Core applications, disrupting business operations and requiring manual restart.

🟠

Likely Case

Application crashes leading to temporary service disruption until automatic or manual restart occurs.

🟢

If Mitigated

Minimal impact with proper network segmentation, rate limiting, and monitoring in place to detect and respond to attacks.

🌐 Internet-Facing: HIGH - Internet-facing .NET Core applications can be directly targeted by attackers without authentication.
🏢 Internal Only: MEDIUM - Internal applications are still vulnerable but require attacker to have internal network access.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Microsoft has not disclosed specific exploitation details, but the vulnerability allows unauthenticated attackers to trigger denial of service.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: .NET Core 5.0.5, 3.1.14, 2.1.27; Visual Studio 2019 version 16.9.4

Vendor Advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-26423

Restart Required: Yes

Instructions:

1. Update .NET Core runtime/SDK to patched versions. 2. Update Visual Studio to version 16.9.4 or later. 3. Rebuild and redeploy applications with updated .NET Core. 4. Restart affected services and applications.

🔧 Temporary Workarounds

Network Segmentation and Filtering

all

Restrict network access to vulnerable applications using firewalls or network security groups

Rate Limiting

all

Implement rate limiting on application endpoints to reduce impact of DoS attempts

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) with DoS protection rules
  • Monitor application health and implement automatic restart mechanisms for crashes

🔍 How to Verify

Check if Vulnerable:

Check .NET Core version with 'dotnet --info' or 'dotnet --version'. Check Visual Studio version via Help > About Microsoft Visual Studio.

Check Version:

dotnet --version

Verify Fix Applied:

Verify installed .NET Core version is 5.0.5+, 3.1.14+, or 2.1.27+. Verify Visual Studio is version 16.9.4+.

📡 Detection & Monitoring

Log Indicators:

  • Application crash logs
  • Unexpected process termination
  • High error rates in application logs

Network Indicators:

  • Unusual traffic patterns to .NET Core applications
  • Multiple connection attempts from single sources

SIEM Query:

source="application_logs" AND ("crash" OR "terminated" OR "unhandled exception") AND process="dotnet"

🔗 References

📤 Share & Export