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

[veracode-workflow-app-preprod]

vulnado-CreateIssues//src/main/java/com/scalesec/vulnado/User.java

Lines 44 to 54 in e82fbd3

	stmt = cxn.createStatement();
	System.out.println("Opened database successfully");
	String query = "select * from users where username = '" + un + "' limit 1";
	System.out.println(query);
	ResultSet rs = stmt.executeQuery(query);
	if (rs.next()) {
	String user_id = rs.getString("user_id");
	String username = rs.getString("username");
	String password = rs.getString("password");
	user = new User(user_id, username, password);

Filename: User.java

Line: 49

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 query. 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