Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Security Management //

Patch Management

4/2/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Drupal RCE Vulnerability Requires Immediate Patching

A remote code execution vulnerability in several versions of Drupal's content management platform requires immediate patching by users. For its part, Drupal is getting out in front of this problem.

Drupal, the widely popular content management system for websites, has been found to have a "highly critical" remote code execution (RCE) vulnerability that requires immediate patching.

The vulnerability (CVE-2018-7600) could allow complete takeover of the affected site from "multiple attack vectors," according to the Drupal team. It has a risk score of 21/25.

The result of the problem is that any visitor, no matter what privileges that they have been assigned, can gain access to, modify and delete private data.

(Source: Flickr)
(Source: Flickr)

According to Drupal, the RCE affects the Bootstrap system. The file that needs patching is located in /apps/drupalhome/includes/bootstrap.inc. The developer team also notes that the vulnerability is activated through either maliciously formed cookies, POST requests or query strings. That would mean that the maintenance page or the user/login may also be vulnerable. So, simply turning the site maintenance mode active will not work since that module uses Bootstrap.

It seems that the vulnerability lies within the logic of Drupal's PHP code -- in that it does not allow for necessary input validation.

Drupal has written in a FAQ section that this RCE problem is not currently active in the wild. However, engineers do expect attackers to develop exploits very soon after the announcement, hence their advice to immediately upgrade or patch.

The problem affects versions 6,7, and 8. Version 7.58 and 8.51 are the latest Drupal versions, and are deemed by Drupal not to have the RCE problem. Since Drupal 6 is on end-of-life status, Drupal recommends contacting the long-term D6 vendors for support and patches.

Patches are also available if immediate upgrading cannot be accomplished, but Drupal does recommend that their use only be temporary until a full upgrade can be performed.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

If patching cannot be done immediately, Drupal points to other mitigation methods.

These methods are all based on the idea of not serving vulnerable Drupal pages to visitors. According to Drupal:

Temporarily replacing your Drupal site with a static HTML (ed. -- static here means an invariant page with no database accessing performed) page is an effective mitigation. For staging or development sites you could disable the site or turn on a "Basic Auth" password to prevent access to the site.

Cloudflare has pushed out a Drupal Web Application Firewall Rule to address the exploit. This doesn't directly help Nginx or Apache users, however.

The Drupal response to the RCE is seemingly exactly what one would want to happen. The team acted responsibly by not hiding it or downplaying it, and have provided a wide range of ways to mediate the problem.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-0235
PUBLISHED: 2022-01-16
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
CVE-2022-0238
PUBLISHED: 2022-01-16
phoronix-test-suite is vulnerable to Cross-Site Request Forgery (CSRF)
CVE-2021-44537
PUBLISHED: 2022-01-15
ownCloud owncloud/client before 2.9.2 allows Resource Injection by a server into the desktop client via a URL, leading to remote code execution.
CVE-2021-33828
PUBLISHED: 2022-01-15
The files_antivirus component before 1.0.0 for ownCloud mishandles the protection mechanism by which malicious files (that have been uploaded to a public share) are supposed to be deleted upon detection.
CVE-2021-33827
PUBLISHED: 2022-01-15
The files_antivirus component before 1.0.0 for ownCloud allows OS Command Injection via the administration settings.