High severityPythonHardcoded SecretsMEDIUM confidence
Django Databases Password Literal
A database PASSWORD is hardcoded in the Django DATABASES configuration (CWE-798).
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)V2.10.4 (L2)
Vulnerable vs. safe
Flagged by this check
DATABASES = {"default": {"ENGINE": "django.db.backends.postgresql", "PASSWORD": "prodDbPass123"}}Passes - the safe pattern
DATABASES = {"default": {"ENGINE": "django.db.backends.postgresql", "PASSWORD": os.environ["DB_PASSWORD"]}}Why it matters & how to fix it
A database PASSWORD is hardcoded in the Django DATABASES configuration (CWE-798). Committing DB credentials exposes the datastore. Populate PASSWORD from os.environ (or django-environ) and rotate the exposed value.
References
Rule ID integsec-python-django-databases-password-literal - 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 - Hardcoded SecretsBasic Auth Credentials In URL
- JavaScript / TypeScript - Hardcoded SecretsDB Connection String With Credentials
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Credential String
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Crypto Key Or IV
- Python - Hardcoded SecretsBasic Auth Credentials In URL
- Python - Hardcoded SecretsDB Connection String Credentials