The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction
None
UI
The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
None
C
There is no impact on the confidentiality of the system; the attacker does not gain the ability to read any data.
Integrity
High
I
There is a total compromise of system integrity. There is a complete loss of system protection, resulting in the attacker being able to modify any file on the target system.
Availability
None
A
There is no impact on the availability of the system; the attacker does not have the ability to disrupt access to or use of the system.
View online: https://drupal.org/node/2194589
* Advisory ID: DRUPAL-SA-CONTRIB-2014-013
* Project: Chaos tool suite (ctools) [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2014-02-12
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
This module provides content editors with an autocomplete callback for entity
titles, as well as an ability to embed content within the Chaos tool suite
(ctools) framework.
Prior to this version, ctools did not sufficiently check access grants for
various types of content other than nodes. It also didn't sufficiently check
access before displaying content with the relationship plugin.
These vulnerabilities are mitigated by the fact that you must be using
entities other than node or users for the autocomplete callback, or you must
be using the relationship plugin and displaying the content (e.g. in panels).
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Chaos tool suite (ctools) 6.x-1.x versions prior to 6.x-1.11.
* Chaos tool suite (ctools) 7.x-1.x versions prior to 7.x-1.4.
Drupal core is not affected. If you do not use the contributed Chaos tool
suite (ctools) [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Chaos tool suite module for Drupal 6.x, upgrade to ctools
6.x-1.11 [5]
* If you use the Chaos tool suite module for Drupal 7.x, upgrade to ctools
7.x-1.4 [6]
Also see the Chaos tool suite (ctools) [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Tim Wood [8]
* Heine Deelstra [9] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Jakob Perry [10] the module maintainer
* David Snopek [11]
-------- COORDINATED BY
------------------------------------------------------
* Peter Wolanin [12] 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 http://drupal.org/contact [13].
Learn more about the Drupal Security team and their policies [14], writing
secure code for Drupal [15], and securing your site [16].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [17]
[1] http://drupal.org/project/ctools
[2] http://drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://drupal.org/project/ctools
[5] https://drupal.org/node/2194547
[6] https://drupal.org/node/2194551
[7] http://drupal.org/project/ctools
[8] https://drupal.org/user/457434
[9] https://drupal.org/user/17943
[10] https://drupal.org/user/45640
[11] https://drupal.org/user/266527
[12] http://drupal.org/user/49851
[13] http://drupal.org/contact
[14] http://drupal.org/security-team
[15] http://drupal.org/writing-secure-code
[16] http://drupal.org/security/secure-configuration
[17] https://twitter.com/drupalsecurity
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum