webshop.elsevier.com, XSS, GHDB DORK REPORT SUMMARY 
					Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search 
 
Loading
Netsparker - Scan Report Summary
				 
			 
			
				
					
						
							
								
									TARGET URL
							 
							
								
									https://webshop.elsevier.com/login.cfm?d46 
							 
						 
						
							
								
									SCAN DATE
							 
							
								5/2/2011 10:41:16 PM
							 
						 
						
							
								
									REPORT DATE
							 
							
								5/3/2011 12:08:55 AM
							 
						 
						
							
								
									SCAN DURATION
							 
							
								
								00:25:11
							 
						 
					
				 
				
					
						
Total Requests 
						
					
					
						
Average Speed 
						
						req/sec.
					
				 
				
					
						8
					
						identified
					
						5
					
						confirmed
					
						0
					
						critical
					
						3
					
						informational
				 
			 
			
				
					DORK TESTS 
					DORK TESTS
				 
			 
			
				
					
						
							
								
									PROFILE
							 
							
								Previous Settings
							 
						 
						
							
								
									ENABLED ENGINES
							 
							
								Blind SQL Injection, Boolean SQL Injection, SQL Injection, Cross-site Scripting
							 
						 
					
				 
				
					
						Authentication
					
					
						Scheduled
					
				 
			 
		
		
		
		
			
				
					VULNERABILITIES 
					Vulnerabilities
				 
			 
			
				
					
				 
				
					
					
					
				 
			 
		
		
		
		
			
				
					VULNERABILITY SUMMARY 
					Vulnerability Summary
				 
			 
			
				
					
				 
			 
		
		
		
		Cross-site Scripting
		Cross-site Scripting 
			
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. 
 
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.
External References 
		
			
			
			
			
			Parameters 
			
				
					
						Parameter
					 
					
						Type
					 
					
						Value
					 
				 
				
					
						d46
					 
					
						GET
					 
					
						
					 
				 
				
					
						Query Based
					 
					
						QUERYSTRING
					 
					
						'"--></style></script><script>alert(0x00003C)</script>
					 
				 
			
			Request 
			GET /login.cfm?'"--></style></script><script>netsparker(0x00003C)</script> HTTP/1.1
			Response 
			HTTP/1.1 200 OK
		 
		
		
		Cookie Not Marked As Secure
		Cookie Not Marked As Secure 
			
A Cookie was not marked as secure and transmitted over HTTPS. This means the cookie could potentially be stolen by an attacker who can successfully intercept and decrypt the traffic or following a successful MITM (
Man in the middle ) attack.
			
Impact 
This cookie will be transmitted over a HTTP connection, therefore if this cookie is important (such as a session cookie ) an attacker might intercept it and hijack a victim's session. If the attacker can carry out a MITM attack, he/she can force victim to make a HTTP request to steal the cookie.
Actions to Take 
	
		See the remedy for solution. 
		Mark all cookies used within the application as secure. (If the cookie is not related to authentication or does not carry any personal information you do not have to mark it as secure. )) 
	 
	
 
Mark all cookies used within the application as secure.
Required Skills for Successful Exploitation 
To exploit this issue, the attacker needs to be able to intercept traffic. This generally requires local access to the web server or victim's network. Attackers need to be understand layer 2, have physical access to systems either as way points for the traffic, or locally (have gained access to ) to a system between the victim and the web server.
		
			
			
			
			
			
			
				CFID
			Request 
			GET /login.cfm?d46 HTTP/1.1
			Response 
			HTTP/1.1 200 OK
		 
		
		
		Internal Server Error
		Internal Server Error 
			
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.
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.
		
			
			
			
			
			Parameters 
			
				
					
						Parameter
					 
					
						Type
					 
					
						Value
					 
				 
				
					
						d46
					 
					
						GET
					 
					
						(select sleep(25))a-- 1
					 
				 
			
			Request 
			GET /login.cfm?d46=(select+sleep(25))a--+1 HTTP/1.1
			Response 
			HTTP/1.1 500 The request has exceeded the allowable time limit Tag: cfoutput
		 
		
		
		Auto Complete Enabled
		Auto Complete Enabled 
			"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.
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.
External References 
		
			
			
			
			
			
			
				login_mailto
			Request 
			GET /login.cfm?d46 HTTP/1.1
			Response 
			HTTP/1.1 200 OK
		 
		
		
		Cookie Not Marked As HttpOnly
		Cookie Not Marked As HttpOnly 
			
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.  
	 
	
 
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.
External References 
		
			
			
			
			
			
			
				CFID
			Request 
			GET /login.cfm?d46 HTTP/1.1
			Response 
			HTTP/1.1 200 OK
		 
		
		
		E-mail Address Disclosure
		E-mail Address Disclosure 
			
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 .
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.
External References 
		
			
			
			
			
			Parameters 
			
				
					
						Parameter
					 
					
						Type
					 
					
						Value
					 
				 
				
					
						d46
					 
					
						GET
					 
					
						1;WAITFOR DELAY '0:0:25'--
					 
				 
				
					
						login_customertype
					 
					
						POST
					 
					
						returning_customer
					 
				 
				
					
						login_mailto
					 
					
						POST
					 
					
						netsparker@example.com
					 
				 
				
					
						login_rua
					 
					
						POST
					 
					
						1
					 
				 
				
					
						password
					 
					
						POST
					 
					
						3
					 
				 
				
					
						signup_mailto
					 
					
						POST
					 
					
						netsparker@example.com
					 
				 
				
					
						target
					 
					
						POST
					 
					
						http://webshop.elsevier.com/customer/mydesk.cfm
					 
				 
			
			
			
				webshop@elsevier.com
			Request 
			POST /login.cfm?d46=1;WAITFOR%20DELAY%20%270:0:25%27-- HTTP/1.1
			Response 
			HTTP/1.1 200 OK
		 
		
		
		IIS Version Disclosure
		IIS Version Disclosure 
			
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.
	Configure your web server to prevent information leakage from the SERVER header of its HTTP response.
		
			
			
			
			
			
			
				Microsoft-IIS/7.0
			Request 
			POST /login.cfm?d46 HTTP/1.1
			Response 
			HTTP/1.1 200 OK
		 
		
		
		[Possible] Internal Path Leakage (Windows)
		[Possible] Internal Path Leakage (Windows) 
			
Netsparker identified an internal path in the document. 
			
Impact 
	
	 There is no direct impact however this information can help an attacker either to identify other vulnerabilities or during the exploitation of other identified vulnerabilities.
	
First ensure that this is not a false positive. Due to the nature of the issue. Netsparker could not confirm that this file path was actually the real file path of the target web server.
	
		Error messages should be disabled. 
		Remove this kind of sensitive data from the output. 
	 
External References 
	
			
			
			
			
			
			
				D:\wwwroot\elsevier_Estreet\onError.cfm
			Request 
			GET /login.cfm?d46=(select+sleep(25))a--+1 HTTP/1.1
			Response 
			HTTP/1.1 500 The request has exceeded the allowable time limit Tag: cfoutput