Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') ('SQL Injection') [VID:13]

[veracode-workflow-app-preprod]

verademo-nonvulnerabilities//app/src/main/java/com/veracode/verademo/commands/RemoveAccountCommand.java

Lines 37 to 47 in 6dd9ec4

	action.execute();
	sqlQuery = "SELECT blab_name FROM users WHERE username = '" + blabberUsername + "'";
	Statement sqlStatement = connect.createStatement();
	logger.info(sqlQuery);
	ResultSet result = sqlStatement.executeQuery(sqlQuery);
	result.next();
	/* START EXAMPLE VULNERABILITY */
	String event = "Removed account for blabber " + result.getString(1);
	sqlQuery = "INSERT INTO users_history (blabber, event) VALUES ('" + blabberUsername + "', '" + event + "')";

Filename: RemoveAccountCommand.java

Line: 42

CWE: 89 (Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') ('SQL Injection'))

This database query contains a SQL injection flaw. The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input. An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sqlQuery. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry. Avoid dynamically constructing SQL queries. Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query. Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible. References: CWE OWASP/nDon't know how to fix this? Don't know why this was reported?
Get Assistance from Veracode