CVE-2023-33141

7.5 HIGH

📋 TL;DR

CVE-2023-33141 is a denial-of-service vulnerability in Microsoft's Yet Another Reverse Proxy (YARP) that allows attackers to cause service disruption by sending specially crafted requests. This affects systems running vulnerable versions of YARP, particularly those exposed to untrusted networks. The vulnerability can lead to resource exhaustion and service unavailability.

💻 Affected Systems

Products:
  • Microsoft Yet Another Reverse Proxy (YARP)
Versions: Versions prior to 2.1.0
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: All YARP deployments using vulnerable versions are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service outage for applications behind YARP, potentially affecting multiple downstream services and causing business disruption.

🟠

Likely Case

Degraded performance or temporary unavailability of services proxied through YARP, requiring restart or intervention to restore functionality.

🟢

If Mitigated

Minimal impact with proper rate limiting, request validation, and monitoring in place to detect and block malicious traffic patterns.

🌐 Internet-Facing: HIGH - Internet-facing YARP instances are directly exposed to potential DoS attacks from any source.
🏢 Internal Only: MEDIUM - Internal instances could still be exploited by compromised internal systems or malicious insiders.

🎯 Exploit Status

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

The vulnerability requires sending crafted requests but does not require authentication, making exploitation straightforward for attackers with network access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: YARP 2.1.0 and later

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-33141

Restart Required: Yes

Instructions:

1. Update YARP package to version 2.1.0 or later via NuGet. 2. Rebuild and redeploy your application. 3. Restart the YARP service or hosting application.

🔧 Temporary Workarounds

Rate Limiting Configuration

all

Implement request rate limiting to prevent resource exhaustion attacks.

Configure rate limiting middleware in your YARP setup

Request Validation

all

Add input validation for incoming requests to filter malicious patterns.

Implement custom middleware to validate and sanitize request headers and parameters

🧯 If You Can't Patch

  • Implement network-level protections such as WAF rules to detect and block DoS patterns
  • Isolate YARP instances behind additional reverse proxies with DoS protection capabilities

🔍 How to Verify

Check if Vulnerable:

Check the YARP package version in your project dependencies. If using .NET, check the NuGet package version.

Check Version:

For .NET applications: check the .csproj file or NuGet package manager for Microsoft.ReverseProxy version

Verify Fix Applied:

Verify that YARP version is 2.1.0 or higher in your deployed application.

📡 Detection & Monitoring

Log Indicators:

  • Unusual spike in request failures
  • High resource utilization (CPU/memory) on YARP instances
  • Increased error rates in proxy logs

Network Indicators:

  • Abnormal request patterns to YARP endpoints
  • Sudden increase in traffic volume from single sources

SIEM Query:

source="yarp-logs" AND (error_count > threshold OR request_rate > normal_baseline)

🔗 References

📤 Share & Export