CVE-2022-24464

7.5 HIGH

📋 TL;DR

CVE-2022-24464 is a denial of service vulnerability in .NET and Visual Studio that allows attackers to crash affected applications by sending specially crafted requests. This affects systems running vulnerable versions of .NET Framework, .NET Core, and Visual Studio. The vulnerability can be exploited remotely without authentication.

💻 Affected Systems

Products:
  • .NET Framework
  • .NET Core
  • Visual Studio
Versions: .NET Framework 4.8 and earlier, .NET Core 3.1, 5.0, 6.0; Visual Studio 2019, 2022
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: Applications built with affected .NET versions are vulnerable regardless of hosting platform. ASP.NET applications are particularly at risk.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service disruption of affected applications, potentially affecting multiple services if shared components are targeted, leading to business downtime.

🟠

Likely Case

Targeted application crashes requiring restart, causing temporary service interruption and potential data loss in active sessions.

🟢

If Mitigated

Minimal impact with proper network segmentation and monitoring allowing quick detection and response to attack attempts.

🌐 Internet-Facing: HIGH - Remote unauthenticated exploitation possible against internet-facing applications using vulnerable .NET components.
🏢 Internal Only: MEDIUM - Internal attackers or compromised systems could exploit this to disrupt internal services and applications.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending specially crafted requests to vulnerable endpoints. No authentication required for remote exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: .NET Framework 4.8.1, .NET Core 3.1.23, 5.0.15, 6.0.3; Visual Studio 2019 16.11.18, 2022 17.0.5

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-24464

Restart Required: Yes

Instructions:

1. Apply security updates from Windows Update or Microsoft Update Catalog. 2. For .NET Core, update runtime and SDK packages. 3. For Visual Studio, update through Visual Studio Installer. 4. Restart affected systems and applications.

🔧 Temporary Workarounds

Network Filtering

all

Block suspicious requests at network perimeter or application firewall

Application Hardening

all

Implement request validation and input sanitization in affected applications

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate vulnerable systems
  • Deploy web application firewall with DoS protection rules

🔍 How to Verify

Check if Vulnerable:

Check .NET version with 'dotnet --info' or examine installed programs in Windows. For Visual Studio, check Help > About.

Check Version:

dotnet --info (for .NET Core) or check registry for .NET Framework versions

Verify Fix Applied:

Verify installed version matches patched versions listed in vendor advisory. Test application stability under normal load.

📡 Detection & Monitoring

Log Indicators:

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

Network Indicators:

  • Unusual request patterns to .NET endpoints
  • Spike in failed requests
  • Abnormal traffic to specific ports

SIEM Query:

EventID: 1000 OR EventID: 1001 (Application crashes) AND ProcessName contains 'dotnet' OR 'w3wp'

🔗 References

📤 Share & Export