Title:
======
Kayako Fusion v4.51.1891 - Multiple Web Vulnerabilities
Date:
=====
2013-01-22
References:
===========
http://www.vulnerability-lab.com/get_content.php?id=824
ID: SWIFT-3119
URL: http://dev.kayako.com/browse/SWIFT-3119
VL-ID:
=====
824
Common Vulnerability Scoring System:
====================================
4.1
Introduction:
=============
Kayako Fusion is the world`s leading multi-channel helpdesk solution that enables organizations to deliver a
better customer experience and work more effectively as a team, whatever their size. Whether over email, support
tickets, self-help, live chat or voice, your customers support history is tracked in one place and can be
accessed from anywhere. Proven, powerful and accessible support tools without the expense or rocket science.
(Copy of the Vendor Homepage: http://www.kayako.com/products/fusion/ )
Abstract:
=========
The Vulnerability Laboratory Research Team discovered multiple persistent web vulnerabilities in the Kayako Fusion v4.51.1891 Application.
Report-Timeline:
================
2013-01-04: Researcher Notification & Coordination
2013-01-22: Public Disclosure
Status:
========
Published
Affected Products:
==================
Kayako
Product: Fusion - CMS 4.51.1891
Exploitation-Technique:
=======================
Remote
Severity:
=========
Medium
Details:
========
Multiple persistent input validation vulnerabilities are detected in the Kayako Fusion v4.51.1891 Web Application.
The vulnerability typus allows an attacker to inject own malicious script code in the vulnerable module on application side (persistent).
The first vulnerability is located in the Tickets section when processing to request via the the `Escalation` module the bound
vulnerable add_tags & remove_tags application parameters. The persistent injected script code will be executed directly out of
the `add` section when processing to edit the earlier inserted dbms context.
The secound vulnerability is located in the Base section when processing to request via the `Manage` module the bound vulnerable
`CustomFieldGroup > eMail` application listing. The persistent injected script code will be executed directly out of the `usergroup`
listing when processing to manage the earlier inserted dbms context.
The third vulnerability is located in the Live-Chat section when processing to request via the `Manage` module the bound vulnerable
`Visitor Group Title` application listing. The persistent injected script code will be executed directly out of the `Visitor Group`
listing when processing to manage the earlier inserted dbms context.
The 4th vulnerability is located in the LanguagePhrase section when processing to request via the `Manage` module the bound vulnerable
`search query` (string) application listing. The persistent injected script code will be executed directly out of the `Search Query`
listing when processing to manage the earlier inserted dbms context.
The 5th vulnerability is located in the Staff section when processing to request via the `Manage or Insert` module the bound vulnerable
`staff name or staff group` application parameters. The persistent injected script code will be executed directly out of the `Staff`- or
`Staff Edit` listing when processing to manage the earlier inserted dbms context.
The vulnerabilities can be exploited with a privileged application user account and low or medium required user interaction.
Successful exploitation of the vulnerability result in persistent session hijacking, persistent phishing, external redirect, external malware
loads and persistent vulnerable module context manipulation.
Vulnerable Section(s):
[+] Tickets
[+] Base
[+] Live-Chat
[+] LanguagePhrase
[+] Staff
Vulnerable Module(s):
[+] Escalation/Insert - (Tickets)
[+] CustomFieldGroup/Manage - (Base)
[+] Staff/Insert & /Staff/Edit/1 - (Base)
[+] StaffGroup/Insert - (Base)
[+] LiveChat/Group/Manage - (Live-Chat)
[+] Manage/0 - Search - (LanguagePhrase)
Vulnerable Parameter(s):
[+] Add tags & remove tags
[+] eMail User - Listing (Profile All Sections)
[+] Visitor Group Title & Group Color
[+] Search Query
Proof of Concept:
=================
The persistent inut validation vulnerabilities can be exploited by restricted low or medium privileged application user account with low
required user interaction. For demonstration or reproduce ...
Review: Add tags & remove tags
Group Type
Custom fields must belong to a custom field group, which is further bound to an area of the product, such as ticket creation, live chat,
user, user group etc.
User
Visibility Specify the custom field group visibility, private groups are not visible to users within the client support
center.
Display Order If there are multiple groups within an area, they are sorted using the display order (ascending) specified here.
