You are here
Home > Preporuke > Ranjivost komponente Drupal CMS-a

Ranjivost komponente Drupal CMS-a

  • Detalji os-a: W03, LRH, LDE, LSU, FBS, HPU, MAC, FED, LGE, LUB, VIS, LMV, W08, WN7
  • Važnost: IMP
  • Operativni sustavi: O
  • Kategorije: ALL, W03, WN7, VIS, W08, HPQ, LRH, LDE, LSU, FBS, LFE, LGE, LUB, APL, LMV, WN8, W12

View online:

* Advisory ID: DRUPAL-SA-CORE-2014-004
* Project: Drupal core [1]
* Version: 6.x, 7.x
* Date: 2014-August-06
* Security risk: 13/25 ( Moderately Critical)
AC:None/A:None/CI:None/II:None/E:Proof/TD:100 [2]
* Exploitable from: Remote
* Vulnerability: Denial of service


Drupal 6 and Drupal 7 include an XML-RPC endpoint which is publicly available
(xmlrpc.php). The PHP XML parser used by this XML-RPC endpoint is vulnerable
to an XML entity expansion attack and other related XML payload attacks which
can cause CPU and memory exhaustion and the site’s database to reach the
maximum number of open connections. Any of these may lead to the site
becoming unavailable or unresponsive (denial of service).

All Drupal sites are vulnerable to this attack whether XML-RPC is used or

In addition, a similar vulnerability exists in the core OpenID module (for
sites that have this module enabled).

This is a joint release as the XML-RPC vulnerability also affects WordPress
(see the announcement [3]).


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


* Drupal core 7.x versions prior to 7.31.
* Drupal core 6.x versions prior to 6.33.


Install the latest version:

* If you use Drupal 7.x, upgrade to Drupal core 7.31 [5].
* If you use Drupal 6.x, upgrade to Drupal core 6.33 [6].

If you are unable to install the latest version of Drupal immediately, you
can alternatively remove the xmlrpc.php file from the root of Drupal core (or
add a rule to .htaccess to prevent access to xmlrpc.php) and disable the
OpenID module. These steps are sufficient to mitigate the vulnerability in
Drupal core if your site does not require the use of XML-RPC or OpenID
functionality. However, this mitigation will not be effective if you are
using a contributed module that exposes Drupal’s XML-RPC API at a different
URL (for example, the Services module); updating Drupal core is therefore
strongly recommended.

Also see the Drupal core [7] project page.


* Willis Vandevanter [8]
* Nir Goldshlager [9]


* Andrew Nacin [10] of the WordPress Security Team
* Michael Adams [11] of the WordPress Security Team
* Frédéric Marand [12]
* David Rothstein [13] of the Drupal Security Team
* Damien Tournoud [14] of the Drupal Security Team
* Greg Knaddison [15] of the Drupal Security Team
* Stéphane Corlosquet [16] of the Drupal Security Team
* Dave Reid [17] of the Drupal Security Team


* The Drupal Security Team [18] and the WordPress [19] Security Team


The Drupal security team can be reached at security at or via the
contact form at [20].

Learn more about the Drupal Security team and their policies [21], writing
secure code for Drupal [22], and securing your site [23].


Security-news mailing list
Unsubscribe at

AutorTomislav Protega
Cert idNCERT-REF-2014-08-0005-ADV
ID izvornikaDRUPAL-SA-CORE-2014-004
More in Preporuke
Ranjivosti jezgre operacijskog sustava

Otkriveno je više ranjivosti u jezgri operacijskog sustava RHEL 7. Ranjivosti su pronađene u podsustavima ptrace i mac80211, implementacijama Netlink,...