Medium severityPythonInsecure ConfigurationMEDIUM confidence
Secure SSL Redirect False
Django is configured without HTTPS enforcement (SECURE_SSL_REDIRECT=False or SECURE_HSTS_SECONDS=0, CWE-16/CWE-319), allowing plaintext HTTP traffic.
Standards mapping
- OWASP Top 10
- A05:2021 - Security Misconfiguration
- OWASP ASVS
- V9.1.1 (L1)
Vulnerable vs. safe
Flagged by this check
SECURE_SSL_REDIRECT = FalsePasses - the safe pattern
SECURE_SSL_REDIRECT = TrueWhy it matters & how to fix it
Django is configured without HTTPS enforcement (SECURE_SSL_REDIRECT=False or SECURE_HSTS_SECONDS=0, CWE-16/CWE-319), allowing plaintext HTTP traffic. Set SECURE_SSL_REDIRECT=True and a non-zero SECURE_HSTS_SECONDS to force HTTPS.
References
Rule ID integsec-python-secure-ssl-redirect-false - 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