We are using the newest version of CRE Loaded 6.4 B2B.
We have quite a few errors which I'll list below:
1.
SQL injection vulnerability in parameter
Web Services :: Saint Port 80
Solution:
All user-supplied parameters should be checked for illegal characters, such as a single quote ('), before being used in an SQL query. See the references below for fix information for specific products.
Information from Target:
Service: http
Sent:
GET /survey.php?id=' HTTP/1.0
Host:
www.****.comUser-Agent: Mozilla/4.0
Connection: Keep-alive
Received:
<b>Parse error</b>: syntax error, unexpected $end, expecting ')' in <b>/home/******/public_html/********/includes/m1_common_function
2. Script allows SQL injection (CactuShop)
Web Services :: Saint Port 80
Solution:
All user-supplied parameters should be checked for illegal characters, such as a single quote ('), before being used in an SQL query. See the references below for fix information for specific products.
CVSS Information:
Low Attack Complexity, Partial Confidentiality Impact, Partial Integrity Impact, Complete Availability Impact
Additional References:
Secunia-11272,Bugtraq-10019,OSVDB-4786,OSVDB-4785,SECTRACK:1009601
Information from Target:
Service: http
Sent:
POST /payonline.asp HTTP/1.0
Host:
www.********.comContent-length: 347
strAgain=yes&CD_EmailAddress=dummy@someemailservice.com&CD_Password=&CD_AffiliateID=&CD_CardholderCountry=200&CD_ShippingCountry=200&CD_ShippingPostcode=&strPaymentSystem=email&CP_CouponCode=&numLanguageID=1&numCurrencyID=1&numItemCount=2&strItems=214;+exec+master..xp_cmdshell+'dir+c:'--z165z&strQuantities=6z2z&numShipMethod=1&btnProceed=Proceed
Received:
<p class="hint">* Hint for webmaster: You can edit this text by editing m1_seourls.error.php in root directory of your store.</p>
3.
Cross-site scripting vulnerability in searchFor parameter to /search.php?test=query
Web Services :: Saint Port 80
Cross-site scripting can be fixed either by creating a customized error page which does not display the URI, or by applying one of the following fixes:
Information from Target:
Service: http
Sent:
GET /M1-Site-Map?CDpath=<script>alert('SAINT')</script> HTTP/1.0
Host:
www.avcdistributor.comUser-Agent: Mozilla/4.0
Connection: Keep-alive
Received:
<td align="center" class="boxText"><div class="infoBoxHeadingHeader">Currencies</div><form name="currencies" action="http://www.*******.com/m1_sitemap.php" method="get"><select name="currency" onChange="this.form.submit();"><option value="USD" selected="selected">US Dollar</option></select><input type="hidden" name="CDpath" value="<script>alert(\'SAINT\')</script>"><input type="hidden" name="osCsid" value="ccd7eb06e5fecbc1eecc5a492cb6122a"></form></td>
4.
web program allows cross-site scripting in query string (/forum/links.php)
Web Services :: Saint Port 80
Cross-site scripting can be fixed either by creating a customized error page which does not display the URI, or by applying one of the following fixes:
Information from Target:
Service: https
Sent:
GET /?%3E%3CSCRIPT%3Ealert('SAINT')%3C/SCRIPT%3E HTTP/1.0
Host:
www.*******.comUser-Agent: Mozilla/4.0
Connection: Keep-alive
Received:
<td align="center" class="boxText"><div class="infoBoxHeadingHeader">Currencies</div><form name="currencies" action="https://www.*******.com/index.php" method="get"><select name="currency" onChange="this.form.submit();"><option value="USD" selected="selected">US Dollar</option></select><input type="hidden" name="><SCRIPT>alert(\'SAINT\')</SCRIPT>" value=""><input type="hidden" name="osCsid" value="80174c344140d4eeb2403325d45df2cc"></form></td>
Now we also had the below issue show up as an issue with our scan but the below issue was related to tracing which our host said was something they could fix and claims they have. We have not done another scan yet but should find out. I don't think it would fix also any of the above issues but for reference here is the one that was fixed:
Web server allows cross-site tracing
Web Services :: Saint Port 80
Solution:
Cross-site tracing can be fixed by disabling the TRACE request method. If this is not an option for your web server, install a vendor fix or use one of the following workarounds:
Information from Target:
Service: http
Sent:
TRACE / HTTP/1.0
Cookie: SAINTtest
Received:
Cookie: SAINTtest
Thank you for any help you can offer. it seems maybe the fix could help these sql injections but we do have some other issues. I hope they aren't anything hard to fix but would something like the os commerce forums solution help or is there another solution I could look into? Or could these even be false positives?