Vulnerability found in Service module of Drupal

Ehacking News

Hacker News / Ehacking News 611 Views 0

When a workforce of researchers from Ambionics audited the Service module of Drupal, they discovered an insecure use of unserialize(). Utilizing this vulnerability the exploiters might simply exploit SQL injection and, distant code execution.

The module, Providers is a "standardized answer for constructing API's in order that exterior shoppers can talk with Drupal," it lets you create totally different endpoints with totally different assets, which helps them to ship and fetch info in a number of output codecs. It's at present getting used with round 45,000 lively web sites, and it's the 150th most used plugin of Drupal.

Among the many different options, one of many most important options is that one can management the format of the enter/output by simply altering the Content material-Sort/Settle for headers. By default, you possibly can solely use the next enter codecs: software/XML, software/JSON, multipart/form-data, software/vnd.php.serialized.

In line with the Ambionics web site the supply and sinks of the exploitation is, "Even when Drupal lacks simple unserialize() devices, the quite a few endpoints which might be out there in Providers, mixed with the power to ship serialized knowledge, offers a variety of methods to take advantage of the vulnerability: user-submitted knowledge can be utilized in SQL queries, echoed again within the end result, and so forth. Our exploitation focuses on /consumer/login, because it was probably the most used endpoint amongst our shoppers. It's nonetheless potential to assemble an RCE payload that works on any URL, so long as the PHP deserialization is activated."

The safety group on the Drupal took 40 minutes to evaluate the stories introduced by the Ambionics, and suggest an accurate patch. They launched an advisory together with a brand new model have been revealed on 03/08/2017 (Providers - Important - Arbitrary Code Execution - SA-CONTRIB-2017-029).

It's strongly advocate to disable software/vnd.php.serialized in Drupal Providers settings and replace your model as quickly as potential.

Comments