High severityJavaHardcoded SecretsHIGH confidence
JDBC Connection String With Password
A JDBC connection string embeds a database password as a hardcoded literal (CWE-798).
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)V2.10.4 (L2)
Vulnerable vs. safe
Flagged by this check
String url = "jdbc:mysql://db.example.com/app?user=root&password=hunter2pw";Passes - the safe pattern
String safe = "jdbc:mysql://db.example.com/app";Why it matters & how to fix it
A JDBC connection string embeds a database password as a hardcoded literal (CWE-798). The credential ships inside the artifact and cannot be rotated without a redeploy. Move the URL, username, and password to externalized configuration (spring.datasource.* backed by environment variables or a secrets manager) and never commit the password to source.
References
Rule ID integsec-java-jdbc-connection-string-with-password - 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