High severityPythonInsecure ConfigurationMEDIUM confidence
Flask Run Debug True
Flask is started with debug=True (CWE-489), exposing the Werkzeug interactive debugger, which permits remote code execution and leaks source/config.
Standards mapping
- OWASP Top 10
- A05:2021 - Security Misconfiguration
- OWASP ASVS
- V14.3.2 (L1)
Vulnerable vs. safe
Flagged by this check
app.run(debug=True)Passes - the safe pattern
app.run(debug=False)Why it matters & how to fix it
Flask is started with debug=True (CWE-489), exposing the Werkzeug interactive debugger, which permits remote code execution and leaks source/config. Never enable debug in production; gate it behind an environment variable.
References
Rule ID integsec-python-flask-run-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