SQL_Injection issue exists @ src/main/java/org/owasp/webgoat/lessons/sqlinjection/introduction/SqlInjectionLesson8.java in branch main
*The application's log method executes an SQL query with executeUpdate, at line 158 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input name; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: -803324155
The application's injectableQueryConfidentiality method executes an SQL query with executeQuery, at line 78 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input name; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: -1815017
The application's log method executes an SQL query with executeUpdate, at line 158 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input auth_tan; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: 496762689
The application's injectableQueryConfidentiality method executes an SQL query with executeQuery, at line 78 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input auth_tan; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: -276298925*
dimihycks
commented
1 year ago
SQL_Injection issue exists @ src/main/java/org/owasp/webgoat/lessons/sqlinjection/introduction/SqlInjectionLesson8.java in branch main
*The application's log method executes an SQL query with executeUpdate, at line 158 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input name; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: -803324155
The application's injectableQueryConfidentiality method executes an SQL query with executeQuery, at line 78 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input name; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: -1815017
The application's log method executes an SQL query with executeUpdate, at line 158 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input auth_tan; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: 496762689
The application's injectableQueryConfidentiality method executes an SQL query with executeQuery, at line 78 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input auth_tan; this input is then read by the completed method at line 59 of src\main\java\org\owasp\webgoat\lessons\sqlinjection\introduction\SqlInjectionLesson8.java. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.Similarity ID: -276298925*
Severity: High
CWE:89
Vulnerability details and guidance
Checkmarx
Training Recommended Fix
Lines: 59
Code (Line #59):