|
|
>> Lotus Connections Cross Site Scripting and Security Bypass Issues
|
Multiple vulnerabilities have been identified in IBM Lotus Connections, which could allow attackers or malicious users to bypass security restrictions or gain knowledge of sensitive information.
The first issue is caused by input validation errors in Homepage, Blogs, Profiles, Dogear, Activities feed and RTE usage from Forum, and Global Search, which could be exploited to conduct cross site scripting attacks.
The second vulnerability is caused by an error within an unspecified API, which could be exploited to inject script into entry descriptions.
The third issue is caused due to incorrect changes being made to a "web.xml" for Activities, which leads to unrestricted access of public seedlist.
The fourth vulnerability is caused by an input validation error when processing the "sortField" parameter, which could allow SQL injection attacks.
The fifth issue is caused by an input validation error when processing community title, which could allow cross-server scripting attacks.
The sixth vulnerability is caused due to the search-admin user's password being exposed in "trace.log".
The seventh issue is caused due to the SMTP password being left in "lcinstalllog.txt".
The eighth weakness is caused due to a password leak in wp_portal.properties, install log, and uninstall log.
Other unspecified password leaks have also been reported.
Affected Products
IBM Lotus Connections versions prior to 2.0.1
Solution
Upgrade to IBM Lotus Connections version 2.0.1 :
http://www-933.ibm.com/eserver/support/fixes/?select0=2&select1=Lotus%20Connections
References
http://www.vupen.com/english/advisories/2008/2968
http://www-01.ibm.com/support/docview.wss?uid=swg27014008
Credits
Vulnerabilities reported by the vendor.
ChangeLog
2008-10-30 : Initial release
Vulnerability Management
Subscribe to VUPEN VNS and receive real-time e-mail and SMS alerts when new advisories or patches relevant to your systems and network configurations are available.
Feedback
If you have additional information or corrections for this security advisory please submit them via our contact form. | |
|
