Call to 'Statement.execute()' with non-constant string
Reports calls to java.sql.Statement.execute()
or any of its variants which take a dynamically-constructed string as the query to execute.
Constructed SQL statements are a common source of security breaches. By default, this inspection ignores compile-time constants.
Example:
ResultSet execute(Statement statement, String name) throws SQLException {
return statement.executeQuery("select * from " + name); // reports warning
}
- 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.
JDBCExecuteWithNonConstantString
Use the inspection options to consider any static
final
fields as constant. Be careful, because strings like the following will be ignored when the option is enabled:
private static final String SQL = "SELECT * FROM user WHERE name='" + getUserInput() + "'";
Here you can find the description of settings available for the Call to 'Statement.execute()' 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!