Comments - As of May 21, 2011, myLittleSQLAdmin V2.0 Lite r.096 is burned-in with VM's from SoftLayer on Windows 2008 R2 Server, 64 Bit. The current versions is Version 3.7 Release 0069 Build 3883 which has Reflected XSS.
Version Identification - mylittleadmin-for-sql-server-version-2.0-lite-r.096
Version Identification - mylittleadmin-for-sql-server-version-3.7-release-0069-build-3833 - The SKIN Cookie is Vuln to Reflected XSS
The value of the Skin cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload Expression was submitted in the Skin cookie. This input was echoed unmodified in the application's response.
XSS (Cross-site Scripting) allows an attacker to execute a dynamic script (Javascript, VbScript) in the context of the application. This allows several different attack opportunities, mostly hijacking the current session of the user or changing the look of the page by changing the HTML on the fly to steal the user's credentials. This happens because the input entered by a user has been interpreted as HTML/Javascript/VbScript by the browser.
XSS targets the users of the application instead of the server. Although this is a limitation, since it allows attackers to hijack other users' session, an attacker might attack an administrator to gain full control over the application.
Impact
There are many different attacks that can be leveraged through the use of XSS, including:
Hi-jacking users' active session
Changing the look of the page within the victims browser.
Mounting a successful phishing attack.
Intercept data and perform man-in-the-middle attacks.
Remedy
The issue occurs because the browser interprets the input as active HTML, Javascript or VbScript. To avoid this, all input and output from the application should be filtered. Output should be filtered according to the output format and location. Typically the output location is HTML. Where the output is HTML ensure that all active content is removed prior to its presentation to the server.
Prior to sanitizing user input, ensure you have a pre-defined list of both expected and acceptable characters with which you populate a white-list. This list needs only be defined once and should be used to sanitize and validate all subsequent input.
There are a number of pre-defined, well structured white-list libraries available for many different environments, good examples of these include, OWASP Reform and Microsoft Anti Cross-site Scripting libraries are good examples.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> Driver={SQL Server};Server=</a style=x:expre/**/ssion(netsparker(0x0003E5))>;Address=</a style=x:expre/**/ssion(netsparker(0x0003E5))>,3;Network =3;Database=3;Trusted_Connection=yes;Uid=3;Pwd=3; </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> dsn='"--></style></script><script>netsparker(0x000410)</script>;uid=3;pwd=3 </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> dsn=3;uid=3;pwd='"--></style></script><script>netsparker(0x000411)</script> </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> dsn=3;uid=<script>ns(0x00043A)</script>;pwd=3 </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> Driver={SQL Server};Server=3;Address=3,3;Network ='"--></style></script><script>netsparker(0x000460)</script>;Database=3;Trusted_Connection=yes;Uid=3;Pwd=3; </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> Driver={SQL Server};Server=3;Address=3,'"--></style></script><script>netsparker(0x00046A)</script>;Network =3;Database=3;Trusted_Connection=yes;Uid=3;Pwd=3; </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> Driver={SQL Server};Server=3;Address=3,3;Network =3;Database="><net sparker=netsparker(0x0003EE)>;Trusted_Connection=yes;Uid=3;Pwd=3; </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
Netsparker confirmed this vulnerability by analyzing the execution of injected JavaScript.
Permanent XSS (Cross-site Scripting) allows an attacker to execute dynamic scripts (Javascript, VbScript) in the context of the application. This allows several different attack opportunities, mostly hijacking the current session of the user or changing the look of the page by changing the HTML on the fly and to steal the user's credentials. This happens because the input entered by the user has been interpreted by HTML/Javascript/VbScript within the browser.
Permanent means that the attack will be stored in the back-end system. In normal XSS attacks an attack needs to e-mail the victim but in a permanent XSS an attacker can just execute the attack and wait for users to see the affected page. As soon as someone visits the page, the attacker's stored payload will get executed.
XSS targets the users of the application instead of the server. Although this is a limitation, since it only allows attackers to hijack other users' session the attacker might attack an administrator to gain full control over the application.
Impact
Permanent XSS is a dangerous issue that has many exploitation vectors, some of which includes:
User session sensitive information such as cookies can be stolen.
XSS can enable client-side worms which could modify, delete or steal other users' data within the application.
The website can be redirected to a new location, defaced or used as a phishing site.
Remedy
The issue occurs because the browser interprets the input as active HTML, Javascript or VbScript. To avoid this, all input and output from the application should be filtered. Output should be filtered according to the output format and location. Typically the output location is HTML. Where the output is HTML ensure that all active content is removed prior to its presentation to the server.
Prior to sanitizing user input, ensure you have a pre-defined list of both expected and acceptable characters with which you populate a white-list. This list needs only be defined once and should be used to sanitize and validate all subsequent input.
There are a number of pre-defined, well structured white-list libraries available for many different environments, good examples of these include, OWASP Reform and Microsoft Anti Cross-site Scripting libraries are good examples.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> dsn='"--></style></script><script>netsparker(0x000410)</script>;uid=3;pwd=3 </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
</BODY> </HTML>
Identification Response
HTTP/1.1 200 OK Cache-Control: no-cache, must-revalidate,private Pragma: no-cache Content-Type: text/html; Charset=iso-8859-1 Content-Encoding: Expires: Tue, 24 Sep 1991 02:00:00 GMT Last-Modified: 5/21/2011 11:47:55 AM Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Sat, 21 May 2011 16:47:55 GMT Content-Length: 1570
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Language" CONTENT="en-FX"> <TITLE>myLittleTools.net :: myLittleAdmin (for SQL Server and MSDE) v.2.0 lite r.096</TITLE> <META NAME="description" CONTENT="myLittleTools.net is a leading provider of web-based applications and components for ASP developers."> <META NAME="author" CONTENT="Elian Chrebor"> <META NAME="reply-to" CONTENT="webmaster@myLittleTools.net"> <META NAME="owner" CONTENT="webmaster@myLittleTools.net"> <META NAME="copyright" CONTENT="(c) 2000-2003, Elian Chrebor, myLittleTools.net"> <LINK REV=made HREF="mailto:webmaster@myLittleTools.net"> <META NAME="ROBOTS" CONTENT="noindex, nofollow"> <LINK REL="stylesheet" HREF="../../themes/classic/css/mla_sql.css" TYPE="text/css"> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript" SRC="../js/mla_sql.js"></SCRIPT> </HEAD> <BODY>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> dsn='"--></style></script><script>netsparker(0x000410)</script>;uid=3;pwd=3 </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
Netsparker identified that password data is sent over HTTP.
Impact
If an attacker can intercept network traffic he/she can steal users credentials.
Actions to Take
See the remedy for solution.
Move all of your critical forms and pages to HTTPS and do not serve them over HTTP.
Remedy
All sensitive data should be transferred over HTTPS rather than HTTP. Forms should be served over HTTPS. All aspects of the application that accept user input starting from the login process should only be served over HTTPS.
Permanent XSS (Cross-site Scripting) allows an attacker to execute dynamic scripts (Javascript, VbScript) in the context of the application. This allows several different attack opportunities, mostly hijacking the current session of the user or changing the look of the page by changing the HTML on the fly and to steal the user's credentials. This happens because the input entered by the user has been interpreted by HTML/Javascript/VbScript within the browser.
Permanent means that the attack will be stored in the back-end system. In normal XSS attacks an attack needs to e-mail the victim but in a permanent XSS an attacker can just execute the attack and wait for users to see the affected page. As soon as someone visits the page, the attacker's stored payload will get executed.
XSS targets the users of the application instead of the server. Although this is a limitation, since it only allows attackers to hijack other users' session the attacker might attack an administrator to gain full control over the application.
Impact
Permanent XSS is a dangerous issue that has many exploitation vectors, some of which includes:
User session sensitive information such as cookies can be stolen.
XSS can enable client-side worms which could modify, delete or steal other users' data within the application.
The website can be redirected to a new location, defaced or used as a phishing site.
Remedy
The issue occurs because the browser interprets the input as active HTML, Javascript or VbScript. To avoid this, all input and output from the application should be filtered. Output should be filtered according to the output format and location. Typically the output location is HTML. Where the output is HTML ensure that all active content is removed prior to its presentation to the server.
Prior to sanitizing user input, ensure you have a pre-defined list of both expected and acceptable characters with which you populate a white-list. This list needs only be defined once and should be used to sanitize and validate all subsequent input.
There are a number of pre-defined, well structured white-list libraries available for many different environments, good examples of these include, OWASP Reform and Microsoft Anti Cross-site Scripting libraries are good examples.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> Driver={SQL Server};Server=</a style=x:expre/**/ssion(netsparker(0x0003E5))>;Address=</a style=x:expre/**/ssion(netsparker(0x0003E5))>,3;Network =3;Database=3;Trusted_Connection=yes;Uid=3;Pwd=3; </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
</BODY> </HTML>
Identification Response
HTTP/1.1 200 OK Cache-Control: no-cache, must-revalidate,private Pragma: no-cache Content-Type: text/html; Charset=iso-8859-1 Content-Encoding: Expires: Tue, 24 Sep 1991 02:00:00 GMT Last-Modified: 5/21/2011 11:47:02 AM Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Sat, 21 May 2011 16:47:02 GMT Content-Length: 1632
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Language" CONTENT="en-FX"> <TITLE>myLittleTools.net :: myLittleAdmin (for SQL Server and MSDE) v.2.0 lite r.096</TITLE> <META NAME="description" CONTENT="myLittleTools.net is a leading provider of web-based applications and components for ASP developers."> <META NAME="author" CONTENT="Elian Chrebor"> <META NAME="reply-to" CONTENT="webmaster@myLittleTools.net"> <META NAME="owner" CONTENT="webmaster@myLittleTools.net"> <META NAME="copyright" CONTENT="(c) 2000-2003, Elian Chrebor, myLittleTools.net"> <LINK REV=made HREF="mailto:webmaster@myLittleTools.net"> <META NAME="ROBOTS" CONTENT="noindex, nofollow"> <LINK REL="stylesheet" HREF="../../themes/classic/css/mla_sql.css" TYPE="text/css"> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript" SRC="../js/mla_sql.js"></SCRIPT> </HEAD> <BODY>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR> Driver={SQL Server};Server=</a style=x:expre/**/ssion(netsparker(0x0003E5))>;Address=</a style=x:expre/**/ssion(netsparker(0x0003E5))>,3;Network =3;Database=3;Trusted_Connection=yes;Uid=3;Pwd=3; </TD></TR> </TABLE> <BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
The Server responded with an HTTP status 500. This indicates that there is a server-side error. Reasons may vary. The behavior should be analysed carefully. If Netsparker is able to find a security issue in the same resource it will report this as a separate vulnerability.
Impact
The impact may vary depending on the condition. Generally this indicates poor coding practices, not enough error checking, sanitization and whitelisting. However there might be a bigger issue such as SQL Injection. If that's the case Netsparker will check for other possible issues and report them separately.
Remedy
Analyse this issue and review the application code in order to handle unexpected errors, this should be a generic practice which does not disclose further information upon an error. All errors should be handled server side only.
"Auto Complete" was enabled in one or more of the form fields. These were either "password" fields or important fields such as "Credit Card".
Impact
Data entered in these fields will be cached by the browser. An attacker who can access the victim's browser could steal this information. This is especially important if the application is commonly used in shared computers such as cyber cafes or airport terminals.
Remedy
Add the attribute autocomplete="off" to the form tag or to individual "input" fields.
Actions to Take
See the remedy for the solution.
Find all instances of inputs which store private data and disable autocomplete. Fields which contain data such as "Credit Card" or "CCV" type data should not be cached. You can allow the application to cache usernames and remember passwords, however, in most cases this is not recommended.
Re-scan the application after addressing the identified issues to ensure that all of the fixes have been applied properly.
Required Skills for Successful Exploitation
Dumping all data from a browser can be fairly easy and there exist a number of automated tools to undertake this. Where the attacker cannot dump the data, he/she could still browse the recently visited websites and activate the auto-complete feature to see previously entered values.
Cookie was not marked as HTTPOnly. HTTPOnly cookies can not be read by client-side scripts therefore marking a cookie as HTTPOnly can provide an additional layer of protection against Cross-site Scripting attacks..
Impact
During a Cross-site Scripting attack an attacker might easily access cookies and hijack the victim's session.
Actions to Take
See the remedy for solution
Consider marking all of the cookies used by the application as HTTPOnly (After these changes javascript code will not able to read cookies.
Remedy
Mark the cookie as HTTPOnly. This will be an extra layer of defence against XSS. However this is not a silver bullet and will not protect the system against Cross-site Scripting attacks. An attacker can use a tool such as XSS Tunnel to bypass HTTPOnly protection.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
Netsparker identified that the TRACE/TRACK method is allowed.
Impact
If the application is vulnerable to Cross-site Scripting and uses Http-Only Cookies then an attacker can bypass the Http-Only cookies limitation and read the cookies in an XSS attack.
Remedy
Disable this method in all production systems. Even though the application is not vulnerable to Cross-site Scripting a debugging feature such as TRACE/TRACK should not be required in a production system and therefore should be disabled.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
Netsparker found e-mail addresses on the web site.
Impact
E-mail addresses discovered within the application can be used by both spam email engines and also brute force tools. Furthermore valid email addresses may lead to social engineering attacks .
Remedy
Use generic email addresses such as contact@ or info@ for general communications, remove user/people specific e-mail addresses from the web site, should this be required use submission forms for this purpose.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>
Netsparker identified that the target web server is disclosing the web server's version in the HTTP response. This information can help an attacker to gain a greater understanding of the system in use and potentially develop further attacks targeted at the specific web server version.
Impact
An attacker can look for specific security vulnerabilities for the version identified through the SERVER header information.
Remediation
Configure your web server to prevent information leakage from the SERVER header of its HTTP response.
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption" COLSPAN=2>Information</TD></TR> <TR><TD CLASS="formlabel">Product :</TD><TD>myLittleAdmin For SQL Server and MSDE</TD></TR> <TR><TD CLASS="formlabel">Version :</TD><TD>2.0 lite</TD></TR> <TR><TD CLASS="formlabel">Release :</TD><TD>096</TD></TR> </TABLE> <BR>
<TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 CLASS="hcontent" SUMMARY="Connection Form" WIDTH=320> <TR><TD CLASS="caption">Navigation</TD></TR> <TR><TD> Use the tree on the left frame to navigate.<BR> <BR> <B>Current connection string :</B><BR>
<H2>Please wait while the tree is loading...</H2> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if (window.parent.frames['Tree']) window.parent.frames['Tree'].document.location = "../inc/tree_con.asp"; --> </SCRIPT>