---------------------------------------------------------------------- A new version (0.9.0.0 - Release Candidate 1) of the free Secunia PSI has been released. The new version includes many new and advanced features, which makes it even easier to stay patched. Download and test it today: https://psi.secunia.com/ Read more about this new version: https://psi.secunia.com/?page=changelog ---------------------------------------------------------------------- TITLE: Layton HelpBox Multiple Vulnerabilities SECUNIA ADVISORY ID: SA27699 VERIFY ADVISORY: http://secunia.com/advisories/27699/ CRITICAL: Moderately critical IMPACT: Cross Site Scripting, Manipulation of data, Exposure of sensitive information, System access WHERE: >From remote SOFTWARE: Layton HelpBox 3.x http://secunia.com/product/3716/ DESCRIPTION: Secunia Research has discovered some vulnerabilities and a weakness in Layton HelpBox, which can be exploited by malicious users to conduct script insertion and SQL injection attacks and compromise a vulnerable system, and by malicious people to identify valid user accounts and conduct cross-site scripting, script insertion, and SQL injection attacks. 1) Improper checks of file extensions in uploadrequest.asp can be exploited to upload arbitrary files. This can e.g. be exploited to upload and execute arbitrary ASP code on a vulnerable system. Successful exploitation of this vulnerability requires valid user credentials. 2) Input passed to the "sys_request_id" parameter in editrequestenduser.asp is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. 3) Input passed to the "oldpassword" parameter in writepwdenduser.asp is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. Successful exploitation of this vulnerability requires valid user credentials. 4) Input passed to the "sys_request_id" parameter in changerequeststatus.asp, editrequestuser.asp, requestcommentsuser.asp, and useractions.asp is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. Successful exploitation of these vulnerabilities require valid analyst credentials. 5) Input passed to the "Asset", "Location", and "Problem" form fields in editrequestenduser.asp is not properly sanitised before being stored. This can be exploited to insert arbitrary HTML and script code, which is executed in a user's browser session in context of an affected site when the malicious data is viewed. Successful exploitation requires that both the attacker and the target user have valid user credentials. 6) Input passed to the "Forename", "Surname", "Telephone", and "Fax" form fields in writeenduserenduser.asp is not properly sanitised before being stored. This can be exploited to insert arbitrary HTML and script code, which is executed in a user's browser session in context of an affected site when the malicious data is viewed. Successful exploitation requires that the target user has valid user credentials. 7) Input passed to the "Asset", "Asset Location", "Problem Desc", and "Solution Desc" form fields in editrequestuser.asp is not properly sanitised before being stored. This can be exploited to insert arbitrary HTML and script code, which is executed in a user's browser session in context of an affected site when the malicious data is viewed. Successful exploitation of this vulnerability requires valid analyst credentials. 8) Input passed to the "Filter" form field in statsrequestypereport.asp and the "sys_request_id" parameter in requestattach.asp is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site. 9) Input passed to the "End User" and "Description" form fields in usersearchrequests.asp is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site. Successful exploitation of this vulnerability requires that the target user has analyst credentials. 10) Different error messages are returned depending on whether an unsuccessful login attempt is performed with a valid or invalid username. The vulnerabilities and the weakness are confirmed in version 3.7.1. Other versions may also be affected. SOLUTION: According to the vendor, the vulnerabilities should be fixed in an upcoming version 4.0. PROVIDED AND/OR DISCOVERED BY: Secunia Research ORIGINAL ADVISORY: Secunia Research: http://secunia.com/secunia_research/2007-94/ ---------------------------------------------------------------------- About: This Advisory was delivered by Secunia as a free service to help everybody keeping their systems up to date against the latest vulnerabilities. Subscribe: http://secunia.com/secunia_security_advisories/ Definitions: (Criticality, Where etc.) http://secunia.com/about_secunia_advisories/ Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor. ---------------------------------------------------------------------- Unsubscribe: Secunia Security Advisories http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org ----------------------------------------------------------------------