CVE-2022-23267

7.5 HIGH

📋 TL;DR

This CVE describes a denial of service vulnerability in .NET and Visual Studio where an attacker could cause affected applications to crash or become unresponsive. The vulnerability affects systems running vulnerable versions of .NET Core, .NET 5, .NET 6, and Visual Studio. Successful exploitation requires the attacker to send specially crafted requests to vulnerable applications.

💻 Affected Systems

Products:
  • .NET Core
  • .NET 5
  • .NET 6
  • Visual Studio
Versions: Specific versions as listed in Microsoft advisory (check patch version for exact ranges)
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: Applications built with affected .NET SDK versions are vulnerable regardless of hosting environment.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Critical applications become completely unavailable, causing business disruption and potential data loss if systems crash during operations.

🟠

Likely Case

Targeted applications experience service degradation or temporary unavailability until restarted.

🟢

If Mitigated

With proper network segmentation and rate limiting, impact is limited to isolated systems with minimal business disruption.

🌐 Internet-Facing: HIGH - Internet-facing applications using affected .NET versions are directly exposed to potential DoS attacks.
🏢 Internal Only: MEDIUM - Internal applications are still vulnerable but require attacker access to internal networks.

🎯 Exploit Status

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

Microsoft rates this as 'Exploitation More Likely' in their advisory. The vulnerability requires sending crafted requests but no authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Microsoft advisory for specific version numbers (e.g., .NET 6.0.3, .NET 5.0.15)

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

Restart Required: Yes

Instructions:

1. Review Microsoft advisory for exact patch versions. 2. Update .NET runtime/SDK to patched version. 3. Update Visual Studio if affected. 4. Rebuild and redeploy applications with updated SDK. 5. Restart affected services.

🔧 Temporary Workarounds

Network Rate Limiting

all

Implement rate limiting on network traffic to vulnerable applications to reduce DoS impact

Application Firewall Rules

all

Configure WAF or firewall to block suspicious patterns targeting .NET applications

🧯 If You Can't Patch

  • Isolate vulnerable systems in segmented network zones
  • Implement aggressive monitoring and alerting for application crashes or performance degradation

🔍 How to Verify

Check if Vulnerable:

Check .NET version with 'dotnet --version' and compare against vulnerable versions in Microsoft advisory

Check Version:

dotnet --version

Verify Fix Applied:

Verify installed .NET version matches or exceeds patched version from Microsoft advisory

📡 Detection & Monitoring

Log Indicators:

  • Unexpected application crashes
  • High CPU/memory usage spikes
  • Increased error rates in application logs

Network Indicators:

  • Unusual traffic patterns to .NET application endpoints
  • High volume of requests from single sources

SIEM Query:

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

🔗 References

📤 Share & Export