exploit the possibilities

SugarCRM 9.0.1 SQL Injection

SugarCRM 9.0.1 SQL Injection
Posted Oct 11, 2019
Authored by EgiX | Site karmainsecurity.com

SugarCRM versions 9.0.1 and below suffer from multiple remote SQL injection vulnerabilities.

tags | exploit, remote, vulnerability, sql injection
MD5 | d7d53f88e5bd5cf9486ffe6a36ff47b3

SugarCRM 9.0.1 SQL Injection

Change Mirror Download
--------------------------------------------------------
SugarCRM <= 9.0.1 Multiple SQL 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) User input passed to the "/pmse_Inbox/changeCaseUser" REST API
endpoint
is not properly sanitized before being used to construct a SQL query.
This can be exploited by malicious users to e.g. read sensitive data
from the database through in-band SQL Injection attacks.

2) User input passed to the "/pmse_Project/CrmData/activities" REST API
endpoint
is not properly sanitized before being used to construct a SQL query.
This can
be exploited by malicious users to e.g. read sensitive data from the
database
through in-band SQL Injection attacks.

3) User input passed to the "/pmse_Project/CrmData/emails" REST API
endpoint is
not properly sanitized before being used to construct a SQL query. This
can be
exploited by malicious users to e.g. read sensitive data from the
database
through in-band SQL Injection attacks.

4) User input passed to the "/pmse_Project/CrmData/emailtemplates" REST
API
endpoint is not properly sanitized before being used to construct a SQL
query.
This can be exploited by malicious users to e.g. read sensitive data
from the
database through in-band SQL Injection attacks.

5) User input passed to the "/pmse_Project/CrmData/users" REST API
endpoint is
not properly sanitized before being used to construct a SQL query. This
can be
exploited by malicious users to e.g. read sensitive data from the
database
through in-band SQL Injection attacks.

6) User input passed through the "pro_module" JSON parameter to the
"/pmse_Project/CrmData/putData" REST API endpoint is not properly
sanitized
before being used to construct a SQL query. This can be exploited by
malicious
users to e.g. read sensitive data from the database through time-based
Blind SQL Injection attacks.

7) User input passed through the "cas_id" and "cas_index" parameters to
the
"/pmse_Project/CrmData/validateReclaimCase" REST API endpoint is not
properly
sanitized before being used to construct a SQL query. This can be
exploited by
malicious users to e.g. read sensitive data from the database through
time-based Blind SQL Injection attacks.

8) The vulnerability exists because the "/modules/Emails/Grab.php"
script is
using the "group_id" field of an "InboundEmail" bean to construct a SQL
query
without being properly sanitized, and such value can be arbitrarily
manipulated
through the MergeRecords module. This can be exploited by malicious
users to
e.g. read sensitive data from the database through boolean-based
second-order
SQL Injection attacks.

9) The vulnerability exists because the "/[module]/export" REST API
endpoint is
using a value that can be arbitrarily manipulated through the
"/[module]/record_list"
endpoint to construct a SQL query without being properly sanitized. This
can be
exploited by malicious users to e.g. read sensitive data from the
database
through in-band second-order SQL Injection attacks.

10) User input passed through the "order_by" parameter to the
"/link/history" REST
API endpoint is not properly sanitized before being used to construct a
SQL query.
This can be exploited by malicious users to e.g. read sensitive data
from the
database through time-based Blind SQL Injection attacks.

11) The vulnerability exists because the
"PersonFormBase::checkForDuplicates()"
method is using certain POST parameters to construct a SQL query without
being
properly sanitized. This can be exploited by malicious users to e.g.
read sensitive
data from the database through time-based SQL Injection attacks.

12) User input passed through the "act_name" JSON parameter to the
"/pmse_Inbox"
REST API endpoint is not properly sanitized before being used to
construct a SQL
query. This can be exploited by malicious users to e.g. read sensitive
data from
the database through time-based Blind SQL Injection attacks.

13) User input passed to the "/pmse_Inbox/processUsersChart" REST API
endpoint is
not properly sanitized before being used to construct a SQL query. This
can be
exploited by malicious users to e.g. read sensitive data from the
database through
in-band SQL Injection attacks. Successful exploitation of this
vulnerability
requires an user account with Admin/Developer access to the "Processes"
module.

14) User input passed through the "deal_tot_discount_percentage" JSON
parameter to
the "/Quotes" REST API endpoint is not properly sanitized before being
used to
construct a SQL query. This can be exploited by malicious users to e.g.
read
sensitive data from the database through time-based Blind SQL Injection
attacks.

15) User input passed through the "q" parameter to the
"/pmse_Inbox/unattendedCases"
REST API endpoint is not properly sanitized before being used to
construct a SQL
query. This can be exploited by malicious users to e.g. read sensitive
data from
the database through in-band SQL Injection attacks. Successful
exploitation of
this vulnerability requires an user account with Admin/Developer access
to
the "Processes" module.

16) User input passed to the "/pmse_Inbox/userListByTeam" REST API
endpoint is not
properly sanitized before being used to construct a SQL query. This can
be exploited
by malicious users to e.g. read sensitive data from the database through
in-band SQL Injection attacks.


[-] 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-04


[-] Other References:

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


Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

October 2019

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Oct 1st
    24 Files
  • 2
    Oct 2nd
    15 Files
  • 3
    Oct 3rd
    7 Files
  • 4
    Oct 4th
    4 Files
  • 5
    Oct 5th
    10 Files
  • 6
    Oct 6th
    1 Files
  • 7
    Oct 7th
    21 Files
  • 8
    Oct 8th
    19 Files
  • 9
    Oct 9th
    5 Files
  • 10
    Oct 10th
    20 Files
  • 11
    Oct 11th
    17 Files
  • 12
    Oct 12th
    4 Files
  • 13
    Oct 13th
    4 Files
  • 14
    Oct 14th
    15 Files
  • 15
    Oct 15th
    19 Files
  • 16
    Oct 16th
    25 Files
  • 17
    Oct 17th
    17 Files
  • 18
    Oct 18th
    7 Files
  • 19
    Oct 19th
    1 Files
  • 20
    Oct 20th
    3 Files
  • 21
    Oct 21st
    12 Files
  • 22
    Oct 22nd
    11 Files
  • 23
    Oct 23rd
    18 Files
  • 24
    Oct 24th
    0 Files
  • 25
    Oct 25th
    0 Files
  • 26
    Oct 26th
    0 Files
  • 27
    Oct 27th
    0 Files
  • 28
    Oct 28th
    0 Files
  • 29
    Oct 29th
    0 Files
  • 30
    Oct 30th
    0 Files
  • 31
    Oct 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2019 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close