[KIS-2019-08] SugarCRM <= 9.0.1 Multiple PHP Object Injection Vulnerabilities

[Egidio Romano <research () karmainsecurity com>]

---------------------------------------------------------------
SugarCRM <= 9.0.1 Multiple PHP Object Injection Vulnerabilities
---------------------------------------------------------------


[-] Software Link:

https://www.sugarcrm.com


[-] Affected Versions:

Version 9.0.1 and prior versions, 8.0.3 and prior versions.


[-] Vulnerabilities Description:

1) The vulnerability exists because the "/modules/Emails/DetailView.php" 
script
is using the unserialize() function with the "campaign_data" field of 
the table,
and such a value can be arbitrarily manipulated through the "save2" 
action. This
can be exploited by malicious users to inject arbitrary PHP objects into 
the
application scope (PHP Object Injection), allowing them to carry out a 
variety
of attacks, such as executing arbitrary PHP code.

2) The vulnerability exists because the 
"/modules/EmailMan/views/view.config.php"
script is using the unserialize() function with the 
"$sugar_config['email_xss']"
variable, and such a value can be arbitrarily manipulated through the 
"Configurator"
module. This can be exploited by malicious users to inject arbitrary PHP 
objects
into the application scope (PHP Object Injection), allowing them to 
carry out a
variety of attacks, such as executing arbitrary PHP code. Successful 
exploitation
of this vulnerability requires a System Administrator account.

3) User input passed through the "ext4" parameter when handling the 
"RefreshField"
action within the "ModuleBuilder" module (when the "type" parameter is 
set to "enum")
is not properly sanitized before being used in a call to the 
unserialize() function.
This can be exploited by malicious users to inject arbitrary PHP objects 
into the
application scope (PHP Object Injection), allowing them to carry out a 
variety of
attacks, such as executing arbitrary PHP code. Successful exploitation 
of this
vulnerability requires an user account with Developer access to any 
module.

4) User input passed through the "ext4" parameter when handling the 
"RefreshField"
action within the "ModuleBuilder" module (when the "type" parameter is 
set to
"multienum") is not properly sanitized before being used in a call to 
the unserialize()
function. This can be exploited by malicious users to inject arbitrary 
PHP objects into
the application scope (PHP Object Injection), allowing them to carry out 
a variety of
attacks, such as executing arbitrary PHP code. Successful exploitation 
of this
vulnerability requires an user account with Developer access to any 
module.

5) The vulnerability exists because the 
"SubPanelDefinitions::get_hidden_subpanels()"
method is using the unserialize() function with the 
"MySettings_hide_subpanels" setting
variable, and such a value can be arbitrarily manipulated through the 
"MergeRecords"
module. This can be exploited by malicious users to inject arbitrary PHP 
objects into
the application scope (PHP Object Injection), allowing them to carry out 
a variety of
attacks, such as executing arbitrary PHP code.

6) The vulnerability exists because the 
"TabController::get_system_tabs()" method is
using the unserialize() function with the "MySettings_tab" setting 
variable, and such
a value can be arbitrarily manipulated through the "MergeRecords" 
module. This can be
exploited by malicious users to inject arbitrary PHP objects into the 
application
scope (PHP Object Injection), allowing them to carry out a variety of 
attacks, such
as executing arbitrary PHP code.

7) The vulnerability exists because the 
"OpportunitySetup::setConfigSetting()" method
is using the unserialize() function with the "MySettings_hide_subpanels" 
setting variable,
and such a value can be arbitrarily manipulated through the 
"MergeRecords" module. This
can be exploited by malicious users to inject arbitrary PHP objects into 
the application
scope (PHP Object Injection), allowing them to carry out a variety of 
attacks,
such as executing arbitrary PHP code.

8) The vulnerability exists because the 
"PackageManager::getinstalledPackages()" method
is using the unserialize() function with the "manifest" field of the 
'upgrade_history'
table, and such a value can be arbitrarily manipulated through the 
"MergeRecords" module.
This can be exploited by malicious users to inject arbitrary PHP objects 
into the
application scope (PHP Object Injection), allowing them to carry out a 
variety of
attacks, such as executing arbitrary PHP code. Successful exploitation 
of this
vulnerability requires a System Administrator account.

9) The vulnerability exists because the 
"UpgradeSavedSearch::__construct()" method is
using the unserialize() function with the "contents" field of the 
'saved_search' table,
and such a value can be arbitrarily manipulated through the 
"MergeRecords" module.
This can be exploited by malicious users to inject arbitrary PHP objects 
into the
application scope (PHP Object Injection), allowing them to carry out a 
variety of
attacks, such as executing arbitrary PHP code.

10) The vulnerability exists because the 
"UserPreference::reloadPreferences()" method
is using the unserialize() function with the "contents" field of the 
'user_preferences'
table, and such a value can be arbitrarily manipulated through the 
"MergeRecords" module.
This can be exploited by malicious users to inject arbitrary PHP objects 
into the
application scope (PHP Object Injection), allowing them to carry out a 
variety of
attacks, such as executing arbitrary PHP code.

11) The vulnerability exists because the "TeamSetManager::cleanUp()" 
method is using the
unserialize() function with the "contents" field of the 
'user_preferences' table, and
such a value can be arbitrarily manipulated through the "MergeRecords" 
module. This can
be exploited by malicious users to inject arbitrary PHP objects into the 
application
scope (PHP Object Injection), allowing them to carry out a variety of 
attacks, such
as executing arbitrary PHP code. Successful exploitation of this 
vulnerability requires
an user account with Admin access to the Users/Teams/Roles modules.

12) User input passed through the "$_FILES['VKFile']" parameter when 
handling the
"LicenseSettings" action within the "Administration" module is not 
properly sanitized
before being used in a call to the unserialize() function within the 
"check_now()"
function. This can be exploited by malicious users to inject arbitrary 
PHP objects
into the application scope (PHP Object Injection), allowing them to 
carry out a variety
of attacks, such as executing arbitrary PHP code. Successful 
exploitation of this
vulnerability requires a System Administrator account.

13) The vulnerability exists because the 
"/modules/Administration/Updater.php" script
is using the unserialize() function with the "license_latest_versions" 
setting variable,
and such a value can be arbitrarily manipulated in different ways. This 
can be exploited
by malicious users to inject arbitrary PHP objects into the application 
scope (PHP
Object Injection), allowing them to carry out a variety of attacks,
such as executing arbitrary PHP code.

14) The vulnerability exists because the 
"/modules/Administration/metadata/adminpaneldefs.php"
script is using the unserialize() function with the 
"license_latest_versions" setting
variable, and such a value can be arbitrarily manipulated in different 
ways. This can
be exploited by malicious users to inject arbitrary PHP objects into the 
application
scope (PHP Object Injection), allowing them to carry out a variety of 
attacks,
such as executing arbitrary PHP code.

15) The vulnerability exists because the "authenticateDownloadKey()" 
function is using the
unserialize() function with the "license_validation_key" setting 
variable, and such a value
can be arbitrarily manipulated in different ways. This can be exploited 
by malicious users
to inject arbitrary PHP objects into the application scope (PHP Object 
Injection), allowing
them to carry out a variety of attacks, such as executing arbitrary PHP 
code.


[-] Solution:

Upgrade to version 9.0.2, 8.0.4, or later.


[-] Disclosure Timeline:

[07/02/2019] - Vendor notified
[01/10/2019] - Versions 9.0.2 and 8.0.4 released
[10/10/2019] - Publication of this advisory


[-] Credits:

Vulnerabilities discovered by Egidio Romano.


[-] Original Advisory:

http://karmainsecurity.com/KIS-2019-08


[-] Other References:

https://support.sugarcrm.com/Documentation/Sugar_Versions/9.0/Ent/Sugar_9.0.2_Release_Notes

_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/