An attacker can repeatedly send crafted requests containing arbitrary, synthetic culture strings to the application. Because these strings are added to the runtime's global cache without adequate throttling or capacity limits, the process memory usage grows indefinitely. This unbounded consumption eventually leads to an out-of-memory (OOM) condition, causing the service to crash or become unresponsive. This flaw affects multiple .NET versions, including 8.0, 9.0, 10.0, and 11.0 previews. Defenders must prioritize patching the .NET SDK and runtime to the specified security versions to mitigate this risk.

Impact

Successful exploitation results in a complete denial of service for affected web applications due to memory exhaustion. The vulnerability is exploitable by unauthenticated remote attackers, making internet-facing ASP.NET Core services highly susceptible to disruption. There are no reports of data exfiltration or arbitrary code execution; however, the ease of triggering memory growth poses a significant risk to availability across all environments (Windows, Linux, and macOS).

Recommendation

• Update all affected ASP.NET Core applications to the patched runtime versions: 8.0.32, 9.0.21, 10.0.13, or 11.0.0-rc.2.
• For self-contained deployments, recompile and redeploy the applications after updating the SDK references to ensure the patch is included in the application bundle.
• Use the dotnet --info command to audit installed runtimes and identify applications requiring maintenance.
• Implement request rate limiting at the web server or load balancer level to mitigate potential automated attempts to exhaust memory until patching can be completed.