osTicket Vulnerabilities
1) Some input isn't 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 a vulnerable site.
Examples:
http://[victim]/view.php?e=test@test.com&t=480826[code]
http://[victim]/include/header.php?osticket_title=%3C/title%3E[code]
http://[victim]/include/admin_login.php?em=asdf[code]
http://[victim]/include/user_login.php?e=asdf[code]
http://[victim]/include/open_submit.php?err=[code]
2) Input passed to the name and subject fields when adding a ticket isn't properly sanitised before being used. This can be exploited to inject arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious user data is viewed.
3) Input passed to the "id" and "cat" parameters isn't properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
Successful exploitation requires user to be authenticated.
4) Input passed to the "include_dir" parameter in "main.php" isn't properly verified, before it is used to include files. This can be exploited to include arbitrary files from external and local resources.
Successful exploitation requires that "register_globals" is enabled.
5) An input validation error in the handling of the "file" parameter in "attachments.php" can be exploited to disclose arbitrary files via directory traversal attacks.
Successful exploitation requires that file uploads are enabled (not default setting).
Solution:
The vulnerabilities have reportedly been fixed by the vendor.
Provided and/or discovered by:
James Bercegay, GulfTech Security Research Team
Source: Secunia
