Multiple vulnerabilities have been discovered in Support Incident Tracker, which can be exploited by malicious users to disclose certain sensitive information, conduct SQL injection attacks and by malicious people to conduct cross-site scripting, cross-site request forgery, and SQL injection attacks.

1) The application's web interface allows users to perform certain actions via HTTP requests without performing any validity checks to verify the requests. This can be exploited to e.g. add an administrator by tricking a logged in administrator into visiting a malicious web site.

2) Input passed via the "mode" parameter to contract_support.php 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.

3) Input passed via the "contractid" parameter to contract_add_service.php 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.

4) Input passed via the "action" parameter to inbox.php 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.

5) Input passed via the "search_string" parameter to incident_add.php (when "action" is set to "findcontact") 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.

6) Input passed via the "table1" parameter to report_customers.php, report_incidents_by_engineer.php, report_incidents_by_site.php, and report_marketing.php 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.

7) Input passed via the "startdate" and "enddate" parameters to report_incidents_by_vendor.php (when "mode" is set) 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.

8) Input passed via the "Referer" header to forgotpwd.php, billable_incidents.php (when "mode" is set to "approvalpage" and "output" is set to "html"), and transactions.php (when "display" is set to "html") 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 via the "contractid" parameter to contract_add_service.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

10) Input passed via the "id" parameter to edit_escalation_path is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

11) Input passed via the "unlock" and "lock" parameters to holding_queue.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

12) Input passed via the "selected" parameter to holding_queue.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

13) Input passed via the "inc" parameter to report_customers.php (when "mode" is set to "report") and report_incidents_by_site.php (when "mode" is set to "report") is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

14) Input passed via the "start" parameter to search.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

15) Input passed via the "sites" parameter to transactions.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

16) Input passed via the "start" parameter to portal/kb.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

17) The "Query By Example" report feature does not properly restrict access to certain database fields when performing reports, which can be exploited to e.g. disclose a password hash of a user.

Successful exploitation of this vulnerability requires access rights to perform "Query By Example" reports (e.g. "Manager" role).

The vulnerabilities are confirmed in version 3.64. Prior versions may also be affected.

Solution
Update to version 3.65.

Provided and/or discovered by
1-16) High-Tech Bridge SA.
17) Reported by the vendor.

Changelog
Further details available to Secunia VIM customers

Original Advisory
HTB23043:
https://www.htbridge.ch/advisory/multiple_vulnerabilities_in_sit_support_incident_tracker.html

Support Incident Tracker:
http://sitracker.org/wiki/ReleaseNotes

Deep Links
Links available to Secunia VIM customers