High severityJavaInjectionMEDIUM confidence
SQL String Concatenation
SQL query is assembled by concatenating a runtime value into the query string (CWE-89).
Standards mapping
- OWASP Top 10
- A03:2021 - Injection
- OWASP ASVS
- V5.3.4 (L1)
Vulnerable vs. safe
Flagged by this check
stmt.executeQuery("SELECT * FROM users WHERE name = " + name);Passes - the safe pattern
PreparedStatement ps = conn.prepareStatement("SELECT * FROM users WHERE name = ?");Why it matters & how to fix it
SQL query is assembled by concatenating a runtime value into the query string (CWE-89). Even when the current input looks trusted, this pattern is fragile and a frequent source of SQL injection. Replace concatenation with a PreparedStatement using bound '?' parameters (or a parameterized JdbcTemplate call).
References
Rule ID integsec-java-sql-string-concat - 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 - InjectionCode Injection Tainted Input
- JavaScript / TypeScript - InjectionEval Dynamic Argument
- JavaScript / TypeScript - InjectionNoSQL Query From Request
- JavaScript / TypeScript - InjectionNoSQL Where Operator
- JavaScript / TypeScript - InjectionOS Command Injection Tainted Input
- JavaScript / TypeScript - InjectionSQL Injection String Concatenation