admin
08-02-2005, 12:42 AM
Kayako LiveResponse
http://www.kayako.com
08-01-2005
http://secunia.com/advisories/16286/
Description:
James Bercegay has reported some vulnerabilities in Kayako LiveResponse, which can be exploited by malicious people to conduct cross-site scripting, script insertion, and SQL injection attacks.
1) Input passed to the "username" parameter in "index.php" 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 an affected site.
2) Input passed to the "year" and "date" parameters in "index.php" isn't properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
3) Input passed to the name in sessions and support messages isn't properly sanitised before being used. This can be exploited to inject arbitrary HTML and script code, which is executed in a user's browser session in context of an affected site when the malicious user data is viewed.
It has also been reported that passwords are sent in clear text in the URL when logging in and the full path to certain scripts can be disclosed when accessed directly.
The vulnerabilities have been reported in version 2.x. Other versions may also be affected.
Solution:
Edit the source code to ensure that input is properly sanitised.
Provided and/or discovered by:
James Bercegay, GulfTech Security Research Team.
Original Advisory:
http://www.gulftech.org/?node=research&article_id=00092-07302005
http://www.kayako.com
08-01-2005
http://secunia.com/advisories/16286/
Description:
James Bercegay has reported some vulnerabilities in Kayako LiveResponse, which can be exploited by malicious people to conduct cross-site scripting, script insertion, and SQL injection attacks.
1) Input passed to the "username" parameter in "index.php" 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 an affected site.
2) Input passed to the "year" and "date" parameters in "index.php" isn't properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
3) Input passed to the name in sessions and support messages isn't properly sanitised before being used. This can be exploited to inject arbitrary HTML and script code, which is executed in a user's browser session in context of an affected site when the malicious user data is viewed.
It has also been reported that passwords are sent in clear text in the URL when logging in and the full path to certain scripts can be disclosed when accessed directly.
The vulnerabilities have been reported in version 2.x. Other versions may also be affected.
Solution:
Edit the source code to ensure that input is properly sanitised.
Provided and/or discovered by:
James Bercegay, GulfTech Security Research Team.
Original Advisory:
http://www.gulftech.org/?node=research&article_id=00092-07302005