|
SugarCRM Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA13287
|
|
|
Release Date:
|
2004-11-24
|
|
Last Update:
|
2005-02-14
|
|
Popularity:
|
7,927 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
Cross Site Scripting
Manipulation of data
Exposure of system information
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Partial Fix
|
|
| Software: | Sugar Sales (formerly SugarCRM) 2.x
SugarCRM 1.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Multiple vulnerabilities have been reported in SugarCRM, which can be exploited by malicious people to conduct cross-site scripting, script insertion and SQL injection attacks, and disclose the content of arbitrary files.
1) Input passed to various scripts and parameters is not properly sanitised before being returned to users. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of a vulnerable site by tricking the user into following a specially crafted link or visit a malicious web site.
Examples:
/index.php?action=UnifiedSearch&module=Home&search_form=false&query _string=[code]
/index.php?module=Accounts&action=ListView&query=true&name=[code]
/index.php?action=index&module=Home&mod_strings[LNK_NEW_CONTACT]=[code]
/modules/Users/Error.php?app_strings[NTC_CLICK_BACK]=[code]
/index.php?module=Contacts&action=EditView&return_module=[code]&return_action=index
/index.php?module=Contacts&action=EditView&return_module=&return_action=[code]
/index.php?name=[code]&action=ListView&query=true&module=Accounts&button=Search
/index.php?action=DetailView&module=Accounts[code]&record=d676f046-1be5-dc36-114e-4138f972bf5d
/index.php?action=DetailView&module=Accounts''''&record=[RECORD_ID][code]
2) User input passed in various fields (e.g. when adding emails, contacts, and accounts) is not sanitised properly before being used. This can be exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in context of a vulnerable site when viewed.
3) Input passed to the "record" parameter in various scripts is not properly sanitised before being used in SQL queries. This can be exploited to manipulate a SQL query by injecting arbitrary SQL code.
Example:
index.php?action=DetailView&module=Accounts&record=[code]
4) Input passed to certain parameters is not properly sanitised before being used to include files. This can be exploited via directory traversal attacks to disclose the content of arbitrary local files.
Examples:
/index.php?module=Opportunities&action=../../../[existing_file]
/index.php?action=DetailView&module=../../../[existing_file]
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
