sartajsinghbhatia007 / CxFlowGitHub

0 stars 0 forks source link

CX Stored_XSS @ root/product.jsp [master] #14

Open sartajsinghbhatia007 opened 1 year ago

sartajsinghbhatia007 commented 1 year ago

Stored_XSS issue exists @ root/product.jsp in branch master

*The application's out.println embeds untrusted data in the generated output with println, at line 49 of root\product.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 42 of root\product.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.

The application's out.println embeds untrusted data in the generated output with println, at line 70 of root\product.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 59 of root\product.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.

The application's out.println embeds untrusted data in the generated output with println, at line 71 of root\product.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 59 of root\product.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.

The application's out.println embeds untrusted data in the generated output with println, at line 79 of root\product.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 59 of root\product.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.*

Severity: High

CWE:79

Checkmarx

Training Recommended Fix

Lines: 42 59


Code (Line #42):

rs = stmt.executeQuery();

Code (Line #59):

rs = stmt.executeQuery();

sartajsinghbhatia007 commented 1 year ago

Issue still exists.