Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-004 | Drupal.org
Skip to search
Can we use first and third party cookies and web beacons to
understand our audience, and to tailor promotions you see
Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-004
Project:
Drupal core
Date:
2018-April-25
Security risk:
Highly critical
20 ∕ 25 AC:Basic/A:User/CI:All/II:All/E:Exploit/TD:Default
Vulnerability:
Remote Code Execution
Affected versions:
>=7.0 <7.59 || >= 8.0.0 <8.4.8 || >=8.5.0 <8.5.3
CVE IDs:
CVE-2018-7602
Description:
A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being compromised. This vulnerability is related to
Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002
. Both SA-CORE-2018-002 and this vulnerability are being exploited in the wild.
Updated — this vulnerability is being exploited in the wild.
Solution:
Upgrade to the most recent version of Drupal 7 or 8 core.
If you are running 7.x, upgrade to
Drupal 7.59
If you are running 8.5.x, upgrade to
Drupal 8.5.3
If you are running 8.4.x, upgrade to
Drupal 8.4.8
. (Drupal 8.4.x is no longer supported and we don't normally provide security releases for
unsupported minor releases
. However, we are providing this 8.4.x release so that sites can update as quickly as possible. You should update to 8.4.8 immediately, then update to 8.5.3 or the latest secure release as soon as possible.)
If you are unable to update immediately, or if you are running a Drupal distribution that does not yet include this security release, you can attempt to apply the patch below to fix the vulnerability until you are able to update completely:
Patch for Drupal 8.x
(8.5.x and below)
Patch for Drupal 7.x
These patches will only work if your site already has the fix from
SA-CORE-2018-002
applied. (If your site does not have that fix,
it may already be compromised
.)
Reported By:
David Rothstein
of the Drupal Security Team
Alex Pott
of the Drupal Security Team
Heine Deelstra
of the Drupal Security Team
Jasper Mattsson
Fixed By:
David Rothstein
of the Drupal Security Team
xjm
of the Drupal Security Team
Samuel Mortenson
of the Drupal Security Team
Alex Pott
of the Drupal Security Team
Lee Rowlands
of the Drupal Security Team
Heine Deelstra
of the Drupal Security Team
Pere Orga
of the Drupal Security Team
Peter Wolanin
of the Drupal Security Team
Tim Plunkett
Michael Hess
of the Drupal Security Team
Nate Lampton
Jasper Mattsson
Neil Drumm
of the Drupal Security Team
Cash Williams
of the Drupal Security Team
Daniel Wehner
Contribution record
Contact and more information
The Drupal security team can be reached by email at security at drupal.org or
via the contact form
Learn more about
the Drupal Security team and their policies
writing secure code for Drupal
, and
securing your site
Follow the Drupal Security Team on
Bluesky
, or
Mastodon
or
Contributing organizations for this advisory
Pantheon
ronder
Thunder
Acquia
Chapter Three (acquired by Kanopi Studios)
Drupal Association
PreviousNext
SciShield
Lullabot
The security team is made up of volunteers around the world. The companies above have sponsored time on this release.
Infrastructure management for Drupal.org provided by
Need a Drupal 7 extended support partner? Consider Tag1.
News items
News
Planet Drupal
Social media
Sign up for Drupal news
Security advisories
Jobs
Our community
Community
Services
Training
Hosting
Contributor guide
Groups & meetups
DrupalCon
Code of conduct
Documentation
Documentation
Drupal Guide
Drupal User Guide
Developer docs
API.Drupal.org
Drupal code base
Download & Extend
Drupal core
Modules
Themes
Distributions
Governance of community
About
Web accessibility
Drupal Association
About Drupal.org
Drupal is a
registered trademark
of
Dries Buytaert