How to fix: ASP.NET error details in page content
ASP.NET error details including stack traces or YSOD (Yellow Screen of Death) are shown to end users.
Why it matters
ASP.NET YSOD pages expose .NET version, file paths, source code lines, and method signatures, information attackers use to identify patched vulnerabilities and target specific versions.
Enable custom error pages in production and disable detailed ASP.NET error output.
How to fix it
- 1Set <customErrors mode="On"> in Web.config
- 2Implement a global exception handler to log and return generic responses
- 3Disable debug mode in production: <compilation debug="false">
Code examples
Use custom errors in ASP.NET web.config
<!-- web.config: suppress detailed errors in production -->
<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="/error">
<error statusCode="404" redirect="/not-found"/>
</customErrors>
</system.web>
</configuration>References
Detected automatically by VulnRadar. The check id is asp-error-in-page, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is ASP.NET error details in page content?
- VulnRadar rates this medium severity in the content 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 asp-error-in-page, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does ASP.NET error details in page content 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.