View online: https://www.drupal.org/SA-CORE-2015-001
* Advisory ID: DRUPAL-SA-CORE-2015-001
* Project: Drupal core [1]
* Version: 6.x, 7.x
* Date: 2015-March-18
* Security risk: 14/25 ( Moderately Critical)
AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2]
* Vulnerability: Access bypass, Open Redirect, Multiple vulnerabilities
-------- DESCRIPTION
---------------------------------------------------------
.... Access bypass (Password reset URLs - Drupal 6 and 7)
Password reset URLs can be forged under certain circumstances, allowing an
attacker to gain access to another user's account without knowing the
account's password.
In Drupal 7, this vulnerability is mitigated by the fact that it can only be
exploited on sites where accounts have been imported or programmatically
edited in a way that results in the password hash in the database being the
same for multiple user accounts. In Drupal 6, it can additionally be
exploited on sites where administrators have created multiple new user
accounts with the same password via the administrative interface, or where
accounts have been imported or programmatically edited in a way that results
in the password hash in the database being empty for at least one user
account.
Drupal 6 sites that have empty password hashes, or a password field with a
guessable string in the database, are especially prone to this vulnerability.
This could apply to sites that use external authentication so that the
password field is set to a fixed, invalid value.
.... Open redirect (Several vectors including the "destination" URL parameter
- Drupal 6 and 7)
Drupal core and contributed modules frequently use a "destination" query
string parameter in URLs to redirect users to a new destination after
completing an action on the current page. Under certain circumstances,
malicious users can use this parameter to construct a URL that will trick
users into being redirected to a 3rd party website, thereby exposing the
users to potential social engineering attacks.
In addition, several URL-related API functions in Drupal 6 and 7 can be
tricked into passing through external URLs when not intending to, potentially
leading to additional open redirect vulnerabilities.
This vulnerability is mitigated by the fact that many common uses of the
"destination" parameter are not susceptible to the attack. However, all
confirmation forms built using Drupal 7's form API are vulnerable via the
Cancel action that appears at the bottom of the form, and some Drupal 6
confirmation forms are vulnerable too.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Drupal core 6.x versions prior to 6.35
* Drupal core 7.x versions prior to 7.35
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Drupal 6.x, upgrade to Drupal core 6.35 [4]
* If you use the Drupal 7.x, upgrade to Drupal core 7.35 [5]
Also see the Drupal core [6] project page.
-------- REPORTED BY
---------------------------------------------------------
Access bypass via password reset URLs:
* Daniël Smidt [7]
Open redirect via vectors including the "destination" URL parameter:
* Hunter Fox [8] of the Drupal Security Team
* Vlad Stratulat [9]
* Michael Smith [10]
* Dave Reid [11] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
Access bypass via password reset URLs:
* Klaus Purer [12] of the Drupal Security Team
* David Rothstein [13] of the Drupal Security Team
* Peter Wolanin [14] of the Drupal Security Team
* Ben Dougherty [15], provisional member of the Drupal Security Team
Open redirect via vectors including the "destination" URL parameter:
* Klaus Purer [16] of the Drupal Security Team
* David Rothstein [17] of the Drupal Security Team
* Hunter Fox [18] of the Drupal Security Team
* Tom Phethean [19], provisional member of the Drupal Security Team
* David Stoline [20] of the Drupal Security Team
* Damien McKenna [21], provisional member of the Drupal Security Team
* Pere Orga [22] of the Drupal Security Team
* Ben Dougherty [23], provisional member of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* The Drupal Security Team [24]
-------- CONTACT AND MORE INFORMATION
----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at https://www.drupal.org/contact [25].
Learn more about the Drupal Security team and their policies [26], writing
secure code for Drupal [27], and securing your site [28].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [29]
[1] https://www.drupal.org/project/drupal
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/drupal-6.35-release-notes
[5] https://www.drupal.org/drupal-7.35-release-notes
[6] https://www.drupal.org/project/drupal
[7] https://www.drupal.org/user/198330
[8] https://www.drupal.org/u/hefox
[9] https://www.drupal.org/user/1006458
[10] https://www.drupal.org/user/1291584
[11] https://www.drupal.org/u/dave-reid
[12] https://www.drupal.org/u/klausi
[13] https://www.drupal.org/u/David_Rothstein
[14] https://www.drupal.org/u/pwolanin
[15] http://drupal.org/u/benjy
[16] https://www.drupal.org/u/klausi
[17] https://www.drupal.org/u/David_Rothstein
[18] https://www.drupal.org/u/hefox
[19] http://drupal.org/user/881620
[20] http://drupal.org/user/329570
[21] https://www.drupal.org/user/108450
[22] https://www.drupal.org/u/pere-orga
[23] http://drupal.org/u/benjy
[24] https://www.drupal.org/security-team
[25] https://www.drupal.org/contact
[26] https://www.drupal.org/security-team
[27] https://www.drupal.org/writing-secure-code
[28] https://www.drupal.org/security/secure-configuration
[29] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2450427
* Advisory ID: DRUPAL-SA-CONTRIB-2015-077
* Project: OG tabs [1] (third-party module)
* Version: 7.x
* Date: 2015-March-11
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
OG Tabs modules provides a secondary menu with links to nodes of the same OG
group.
The module doesn't sufficiently sanitize user supplied text in some pages,
thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have
permission to create/edit nodes posted in an Organic Groups group.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* OG Tabs 7.x-1.x versions prior to 7.x-1.1.
Drupal core is not affected. If you do not use the contributed OG tabs [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the OG Tabs module for Drupal 7.x, upgrade to OG Tabs 7.x-1.1
[5]
Also see the OG tabs [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Adam Sanchez [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Rick Manelius [9] of the Drupal Security Team
* Aaron Ott [10] provisional member 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 https://www.drupal.org/contact [11].
Learn more about the Drupal Security team and their policies [12], writing
secure code for Drupal [13], and securing your site [14].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [15]
[1] https://www.drupal.org/project/og_tabs
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/og_tabs
[5] https://www.drupal.org/node/2404115
[6] https://www.drupal.org/project/og_tabs
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/192617
[9] https://www.drupal.org/user/680072
[10] https://www.drupal.org/user/154069
[11] https://www.drupal.org/contact
[12] https://www.drupal.org/security-team
[13] https://www.drupal.org/writing-secure-code
[14] https://www.drupal.org/security/secure-configuration
[15] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2450393
* Advisory ID: DRUPAL-SA-CONTRIB-2015-076
* Project: Image Title [1] (third-party module)
* Version: 7.x
* Date: 2015-March-11
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Image Title module allows you to upload an image and use it as a node title.
The module doesn't sufficiently sanitize user supplied text in some pages,
thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must allowed to
create/edit nodes.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Image Title 7.x-1.x versions prior to 7.x-1.1
Drupal core is not affected. If you do not use the contributed Image Title
[4] module,
there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Image Title module for Drupal 7.x, upgrade to Image Title
7.x-1.1 [5]
Also see the Image Title [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Deepak Singh [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [9] 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 https://www.drupal.org/contact [10].
Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [14]
[1] https://www.drupal.org/project/image_title
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/image_title
[5] https://www.drupal.org/node/2450015
[6] https://www.drupal.org/project/image_title
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/86382
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/contact
[11] https://www.drupal.org/security-team
[12] https://www.drupal.org/writing-secure-code
[13] https://www.drupal.org/security/secure-configuration
[14] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2450391
* Advisory ID: DRUPAL-SA-CONTRIB-2015-075
* Project: Perfecto [1] (third-party module)
* Version: 7.x
* Date: 2015-March-11
* Security risk: 10/25 ( Moderately Critical)
AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All [2]
* Vulnerability: Open Redirect
-------- DESCRIPTION
---------------------------------------------------------
The Perfecto module allows themers accurately calibrate the CSS by floating
compositions over the page.
The module doesn't sufficiently check user supplied URLs in parameters used
for page redirection. An attacker could trick users to visit malicious sites
without realizing it.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Perfecto 7.x-1.x versions prior to 7.x-1.2.
Drupal core is not affected. If you do not use the contributed Perfecto [4]
module,
there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Perfecto module for Drupal 7.x, upgrade to Perfecto
7.x-1.2
[5]
Also see the Perfecto [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Hannes Kirsman [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [9] 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 https://www.drupal.org/contact [10].
Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [14]
[1] https://www.drupal.org/project/perfecto
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/perfecto
[5] https://www.drupal.org/node/2449877
[6] https://www.drupal.org/project/perfecto
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/1860980
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/contact
[11] https://www.drupal.org/security-team
[12] https://www.drupal.org/writing-secure-code
[13] https://www.drupal.org/security/secure-configuration
[14] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2450387
* Advisory ID: DRUPAL-SA-CONTRIB-2015-074
* Project: Site Documentation [1] (third-party module)
* Version: 6.x
* Date: 2015-March-11
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Site Documentation module enables you to display detailed configuration
information.
The module doesn't sufficiently sanitize user supplied text in some pages,
thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a user
with permission to create/edit taxonomy terms.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Site Documentation 6.x-1.x versions prior to 6.x-1.5.
Drupal core is not affected. If you do not use the contributed Site
Documentation [4] module,
there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Site Documentation module for Drupal 6.x, upgrade to Site
Documentation 6.x-1.5 [5]
Also see the Site Documentation [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Nancy Wichmann [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [9] 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 https://www.drupal.org/contact [10].
Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [14]
[1] https://www.drupal.org/project/sitedoc
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/sitedoc
[5] https://www.drupal.org/node/2450321
[6] https://www.drupal.org/project/sitedoc
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/101412
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/contact
[11] https://www.drupal.org/security-team
[12] https://www.drupal.org/writing-secure-code
[13] https://www.drupal.org/security/secure-configuration
[14] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2446065
* Advisory ID: DRUPAL-SA-CONTRIB-2015-073
* Project: Trick Question [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-March-04
* Security risk: 13/25 ( Moderately Critical)
AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
The Trick Question is a CAPTCHA-type spam prevention module; a lightweight,
compact and simple alternative to larger and more complex modules.
The module doesn't sufficiently sanitize user supplied text in some pages,
thereby exposing a Cross Site Scripting vulnerability.
The vulnerability is mitigated by the fact that an attacker must have the
"Administer Trick Question" permission.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Trick Question 6.x-1.x versions prior to 6.x-1.5
* Trick Question 7.x-1.x versions prior to 7.x-1.5
Drupal core is not affected. If you do not use the contributed Trick Question
[4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Trick Question module for Drupal 6.x, upgrade to Trick
Question 6.x-1.5 [5]
* If you use the Trick Question module for Drupal 7.x, upgrade to Trick
Question 7.x-1.5 [6]
Also see the Trick Question [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Matt Vance [8] provisional member of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Martin Joergensen [9] the module maintainer
* Matt Vance [10] provisional member of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* Matt Vance [11] provisional member 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 https://www.drupal.org/contact [12].
Learn more about the Drupal Security team and their policies [13], writing
secure code for Drupal [14], and securing your site [15].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [16]
[1] https://www.drupal.org/project/trick_question
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/trick_question
[5] https://www.drupal.org/node/2373143
[6] https://www.drupal.org/node/2373147
[7] https://www.drupal.org/project/trick_question
[8] https://www.drupal.org/user/88338
[9] https://www.drupal.org/user/81257
[10] https://www.drupal.org/user/88338
[11] https://www.drupal.org/user/88338
[12] https://www.drupal.org/contact
[13] https://www.drupal.org/security-team
[14] https://www.drupal.org/writing-secure-code
[15] https://www.drupal.org/security/secure-configuration
[16] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2446051
* Advisory ID: DRUPAL-SA-CONTRIB-2015-072
* Project: Commerce Ogone [1] (third-party module)
* Version: 7.x
* Date: 2015-March-04
* Security risk: 13/25 ( Moderately Critical)
AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to use Ogone (Ingenico) as a payment method for
Drupal Commerce.
Malicious users can trick Commerce Ogone into proceeding with the checkout
process without actually going through the Ogone payment process, causing the
order status to be set to checkout complete, even though no payment was
processed.
The vulnerability is mitigated by the fact that the balance to be paid on
affected orders remains the full amount, and no payment transaction is linked
to the order.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Commerce Ogone 7.x-1.x versions prior to 7.x-1.5.
Drupal core is not affected. If you do not use the contributed Commerce Ogone
[4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Commerce Ogone module for Drupal 7.x, upgrade to Commerce
Ogone 7.x-1.5 [5]
Also see the Commerce Ogone [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Mathieu Massebœuf [7]
-------- FIXED BY
------------------------------------------------------------
* Mathieu Massebœuf [8]
* Ivo Van Geertruyen [9] of the Drupal Security Team and module
co-maintainer
-------- COORDINATED BY
------------------------------------------------------
* Klaus Purer [10] of the Drupal Security Team
* Greg Knaddison [11] 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 https://www.drupal.org/contact [12].
Learn more about the Drupal Security team and their policies [13], writing
secure code for Drupal [14], and securing your site [15].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [16]
[1] https://www.drupal.org/project/commerce_ogone
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/commerce_ogone
[5] https://www.drupal.org/node/2445835
[6] https://www.drupal.org/project/commerce_ogone
[7] https://www.drupal.org/user/974302
[8] https://www.drupal.org/user/974302
[9] https://www.drupal.org/user/383424
[10] https://www.drupal.org/user/262198
[11] https://www.drupal.org/user/36762
[12] https://www.drupal.org/contact
[13] https://www.drupal.org/security-team
[14] https://www.drupal.org/writing-secure-code
[15] https://www.drupal.org/security/secure-configuration
[16] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2446019
* Advisory ID: DRUPAL-SA-CONTRIB-2015-071
* Project: Simple subscription [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-March-04
* Security risk: 13/25 ( Moderately Critical)
AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to add a block to allow visitors to subscribe to a
site's newsletter.
The module failed to sanitize some block content, leading to a Cross Site
Scripting (XSS) vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "administer blocks".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Simple Subscription 6.x-1.x versions prior to 6.x-1.1.
* Simple Subscription 7.x-1.x versions prior to 7.x-1.1.
Drupal core is not affected. If you do not use the contributed Simple
Subscription [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Simple Subscription module for Drupal 6.x, upgrade to
Simple Subscription 6.x-1.1 [5]
* If you use the Simple Subscription module in branch 7.x-1.x for Drupal
7.x, upgrade to Simple Subscription 7.x-1.1 [6]
* If you use the Simple Subscription module in branch 7.x-2.x for Drupal
7.x, there is nothing to do, this branch is secure
Also see the Simple Subscription [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Matt Vance [8] provisional member of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Matt Vance [9] provisional member of the Drupal Security Team
* SebCorbin [10] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Michael Hess [11] of the Drupal Security Team
* Matt Vance [12] provisional member of the Drupal Security Team
* Aaron Ott [13] provisional member 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 https://www.drupal.org/contact [14].
Learn more about the Drupal Security team and their policies [15], writing
secure code for Drupal [16], and securing your site [17].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [18]
[1] https://www.drupal.org/project/simple_subscription
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/simple_subscription
[5] https://www.drupal.org/node/2437931
[6] https://www.drupal.org/node/2437933
[7] https://www.drupal.org/project/simple_subscription
[8] https://www.drupal.org/user/88338
[9] https://www.drupal.org/user/88338
[10] https://www.drupal.org/user/412171
[11] https://security.drupal.org/user/14049
[12] https://www.drupal.org/user/88338
[13] https://www.drupal.org/user/154069
[14] https://www.drupal.org/contact
[15] https://www.drupal.org/security-team
[16] https://www.drupal.org/writing-secure-code
[17] https://www.drupal.org/security/secure-configuration
[18] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2445977
* Advisory ID: DRUPAL-SA-CONTRIB-2015-070
* Project: Mover [1] (third-party module)
* Version: 6.x
* Date: 2015-March-04
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
The Mover modules provide the ability to move content between Drupal sites.
The module doesn't sufficiently sanitize user supplied text in some pages,
thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have
permission to create/edit nodes.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Mover 6.x-1.0
Drupal core is not affected. If you do not use the contributed Mover [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
If you use the Mover module you should uninstall it.
Also see the Mover [5] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [6] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
Not applicable.
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [7] 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 https://www.drupal.org/contact [8].
Learn more about the Drupal Security team and their policies [9], writing
secure code for Drupal [10], and securing your site [11].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [12]
[1] https://www.drupal.org/project/mover
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/mover
[5] https://www.drupal.org/project/mover
[6] https://www.drupal.org/user/2301194
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/contact
[9] https://www.drupal.org/security-team
[10] https://www.drupal.org/writing-secure-code
[11] https://www.drupal.org/security/secure-configuration
[12] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2445973
* Advisory ID: DRUPAL-SA-CONTRIB-2015-069
* Project: Taxonomy Accordion [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-March-04
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Taxonomy Accordion module creates a block for each taxonomy vocabularies.
The module doesn't sufficiently sanitize user supplied text in some pages,
thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a user
allowed to create/edit taxonomy terms.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* All versions of Taxonomy Accordion module
Drupal core is not affected. If you do not use the contributed Taxonomy
Accordion [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
If you use the Taxonomy Accordion module you should uninstall it.
Also see the Taxonomy Accordion [5] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [6] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
Not applicable.
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [7] 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 https://www.drupal.org/contact [8].
Learn more about the Drupal Security team and their policies [9], writing
secure code for Drupal [10], and securing your site [11].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [12]
[1] https://www.drupal.org/project/taxonomy_accordion
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/taxonomy_accordion
[5] https://www.drupal.org/project/taxonomy_accordion
[6] https://www.drupal.org/user/2301194
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/contact
[9] https://www.drupal.org/security-team
[10] https://www.drupal.org/writing-secure-code
[11] https://www.drupal.org/security/secure-configuration
[12] https://twitter.com/drupalsecurity