Medium severityC#Insecure ConfigurationHIGH confidence
Compilation Debug True
ASP.NET is configured with <compilation debug="true">, which disables optimizations, leaks detailed diagnostics, and can expose source in error output (CWE-11/CWE-489).
Standards mapping
- OWASP Top 10
- A05:2021 - Security Misconfiguration
- OWASP ASVS
- V14.3.2 (L1)
Vulnerable vs. safe
Flagged by this check
<compilation debug="true" targetFramework="4.8" />Passes - the safe pattern
<compilation debug="false" targetFramework="4.8" />Why it matters & how to fix it
ASP.NET is configured with <compilation debug="true">, which disables optimizations, leaks detailed diagnostics, and can expose source in error output (CWE-11/CWE-489). Set debug="false" for production builds and gate debug settings to development-only configuration transforms.
References
Rule ID integsec.csharp.insecure-config.compilation-debug-true - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Insecure ConfigurationCORS Acao Wildcard Header
- JavaScript / TypeScript - Insecure ConfigurationCORS Wildcard Origin
- JavaScript / TypeScript - Insecure ConfigurationCORS Wildcard With Credentials
- JavaScript / TypeScript - Insecure ConfigurationCSRF Protection Disabled
- JavaScript / TypeScript - Insecure ConfigurationExpress Trust Proxy All
- JavaScript / TypeScript - Insecure ConfigurationExpress X Powered By Enabled