How to fix: ASP.NET Core Developer Exception Page Exposed
The ASP.NET Core Developer Exception Page ('An unhandled exception occurred while processing the request' with Microsoft.AspNetCore references) was found in the response.
Why it matters
This page renders the full exception, stack trace, request headers, cookies, query string, and route data, which is a significant amount of internal and potentially sensitive detail handed directly to any client that triggers an error.
UseDeveloperExceptionPage() is meant to be conditionally registered only when the ASP.NET Core hosting environment is Development. Registering it unconditionally (or misconfiguring ASPNETCORE_ENVIRONMENT) exposes this diagnostic page in production.
How to fix it
- 1Only call app.UseDeveloperExceptionPage() inside an 'if (env.IsDevelopment())' branch.
- 2Use app.UseExceptionHandler("/Error") for all non-development environments.
- 3Verify ASPNETCORE_ENVIRONMENT is set to 'Production' in the deployed environment.
Code examples
Program.cs / Startup.cs
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Error");
app.UseHsts();
}References
Detected automatically by VulnRadar. The check id is dotnet-core-developer-exception-page, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is ASP.NET Core Developer Exception Page Exposed?
- VulnRadar rates this high severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dotnet-core-developer-exception-page, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does ASP.NET Core Developer Exception Page Exposed map to?
- It maps to CWE-209. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.