Call to 'Connection.prepare*()' with non-constant string
Reports calls to java.sql.Connection.prepareStatement()
, java.sql.Connection.prepareCall()
, or any of their variants which take a dynamically-constructed string as the statement to prepare.
Constructed SQL statements are a common source of security breaches. By default, this inspection ignores compile-time constants.
Example:
String bar() { return "bar"; }
Connection connection = DriverManager.getConnection("", "", "");
connection.("SELECT * FROM user WHERE name='" + bar() + "'");
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
JDBCPrepareStatementWithNonConstantString
Use the inspection settings to consider any static
final
fields as constants. Be careful, because strings like the following will be ignored when the option is enabled:
static final String SQL = "SELECT * FROM user WHERE name='" + getUserInput() + "'";
Here you can find the description of settings available for the Call to 'Connection.prepare*()' with non-constant string inspection, and the reference of their default values.
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |
Thanks for your feedback!