[Security-news] Services - Critical - SQL Injection - SA-CONTRIB-2017-054

[security-news at drupal.org]

View online: https://www.drupal.org/node/2890353

   * Advisory ID: DRUPAL-SA-CONTRIB-2017-054
   * Project: Services [1]     (third-party module)
   * Version: 7.x
   * Date: 2017-June-28
   * Security risk: 19/25 ( Critical)
     AC:None/A:User/CI:All/II:All/E:Theoretical/TD:Default [2]
   * Vulnerability: SQL Injection

-------- DESCRIPTION
---------------------------------------------------------

This module provides a standardized solution for building API's so that
external clients can communicate with Drupal.

The module doesn't sufficiently sanitize column names provided by the client
when they are querying for data and trying to sort it.

This vulnerability is mitigated by the fact that a site must have an "Index"
resource enabled and the attacker must know the endpoint's URL.


-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------

   * /A CVE identifier [3] will be requested, and added upon issuance, in
     accordance with Drupal Security Team processes./

-------- VERSIONS AFFECTED
---------------------------------------------------

   * Services 7.x-3.x versions prior to 7.x-3.20

Drupal core is not affected. If you do not use the contributed Services [4]
module, there is nothing you need to do.

-------- SOLUTION
------------------------------------------------------------

Install services version 7.x-3.20 [5] of the module or disable any Index
resources within your endpoint(s).

Also see the Services [6] project page.

-------- REPORTED BY
---------------------------------------------------------

   * John Morahan [7]

-------- FIXED BY
------------------------------------------------------------

   * Tyler Frankenstein [8], a module maintainer
   * John Morahan [9]

-------- COORDINATED BY
------------------------------------------------------

   * Michael Hess [10] of the Drupal Security Team

-------- CONTACT AND MORE INFORMATION
----------------------------------------

The Drupal security team can be reached at security at drupal.org or via the
contact form at https://www.drupal.org/contact [11].

Learn more about the Drupal Security team and their policies [12], writing
secure code for Drupal [13], and  securing your site [14].

Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [15]


[1] https://www.drupal.org/project/services
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/services
[5] https://www.drupal.org/project/services/releases/7.x-3.20
[6] https://www.drupal.org/project/services
[7] https://www.drupal.org/user/58170
[8] https://www.drupal.org/user/XXXUID
[9] https://www.drupal.org/user/58170
[10] https://www.drupal.org/u/mlhess
[11] https://www.drupal.org/contact
[12] https://www.drupal.org/security-team
[13] https://www.drupal.org/writing-secure-code
[14] https://www.drupal.org/security/secure-configuration
[15] https://twitter.com/drupalsecurity