search

sartajsinghbhatia007 / CxFlowGitHub

0 stars 0 forks source link

CX SQL_Injection @ root/basket.jsp [master] #16

Open sartajsinghbhatia007 opened 1 year ago

sartajsinghbhatia007 commented 1 year ago

SQL_Injection issue exists @ root/basket.jsp in branch master

*The application's stmt.execute method executes an SQL query with execute, at line 274 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 223 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 173 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 55 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 188 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 228 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 242 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 166 of root\basket.jsp. 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 getValue; this input is then read by the cookie.getValue method at line 43 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 228 of root\basket.jsp. 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 getParameterMap; this input is then read by the request.getParameterMap method at line 212 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 274 of root\basket.jsp. 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 getParameterMap; this input is then read by the request.getParameterMap method at line 212 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 223 of root\basket.jsp. 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 getParameterMap; this input is then read by the request.getParameterMap method at line 212 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 274 of root\basket.jsp. 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 ""productid""; this input is then read by the request.getParameter method at line 148 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 173 of root\basket.jsp. 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 ""productid""; this input is then read by the request.getParameter method at line 148 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 181 of root\basket.jsp. 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 ""productid""; this input is then read by the request.getParameter method at line 148 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 188 of root\basket.jsp. 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 ""productid""; this input is then read by the request.getParameter method at line 148 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 166 of root\basket.jsp. 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 ""productid""; this input is then read by the request.getParameter method at line 148 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 274 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 223 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 173 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 55 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 188 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.execute method executes an SQL query with execute, at line 228 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 242 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.

The application's stmt.executeQuery method executes an SQL query with executeQuery, at line 166 of root\basket.jsp. 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 getCookies; this input is then read by the request.getCookies method at line 38 of root\basket.jsp. This input then flows through the code, into a query and to the database server - without sanitization.This may enable an SQL Injection attack.*

Severity: High

CWE:89

Checkmarx

Training Recommended Fix

Lines: 212 148 38 43

Code (Line #212):

Map params = request.getParameterMap();

Code (Line #148):

String productId = request.getParameter("productid");

Code (Line #38):

Cookie[] cookies = request.getCookies();

Code (Line #43):

basketId = cookie.getValue();
sartajsinghbhatia007 commented 1 year ago

Issue still exists.