Impact
Boolean-based blind SQL injection vulnerability existed in Time Tracker invoices.php in versions prior to 1.22.11.5781. This was happening because of a coding error after validating parameters in POST requests. There was no check for errors before adjusting invoice sorting order. Because of this, it was possible to craft a POST request with malicious SQL for Time Tracker database.
Patches
Fixed in version 1.22.11.5781.
Workarounds
Upgrade is recommended. If it is not practical, insert an additional check for errors (line 79) in a condition before calling ttGroupHelper::getActiveInvoices()
(line 85) in invoices.php.
References
More invormation about this issue is available on Anuko website at https://www.anuko.com/time-tracker/news/sql-injection-vulnerability-in-invoices.htm
Impact
Boolean-based blind SQL injection vulnerability existed in Time Tracker invoices.php in versions prior to 1.22.11.5781. This was happening because of a coding error after validating parameters in POST requests. There was no check for errors before adjusting invoice sorting order. Because of this, it was possible to craft a POST request with malicious SQL for Time Tracker database.
Patches
Fixed in version 1.22.11.5781.
Workarounds
Upgrade is recommended. If it is not practical, insert an additional check for errors (line 79) in a condition before calling
ttGroupHelper::getActiveInvoices()
(line 85) in invoices.php.References
More invormation about this issue is available on Anuko website at https://www.anuko.com/time-tracker/news/sql-injection-vulnerability-in-invoices.htm