How to fix: Database connection string in source
A database connection string containing credentials is visible in client-accessible source or configuration files.
Why it matters
An exposed database connection string gives an attacker direct access to your database, bypassing all application-level security controls and allowing them to read, modify, or delete all data.
Connection strings must be stored in environment variables or a secrets manager, never in source code or public-facing files.
How to fix it
- 1Immediately rotate the database credentials
- 2Move the connection string to an environment variable or secrets manager
- 3Ensure .env files are in .gitignore and not served by the web server
Code examples
Store connection strings in environment variables
// Unsafe: hardcoded connection string
const pool = new Pool({ connectionString: 'postgresql://user:pass@host/db' });
// Safe: read from environment
const pool = new Pool({ connectionString: process.env.DATABASE_URL });References
Detected automatically by VulnRadar. The check id is database-connection-string, 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 Database connection string in source?
- VulnRadar rates this critical 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 database-connection-string, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Database connection string in source map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07: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.