View online: https://www.drupal.org/node/2459323
* Advisory ID: DRUPAL-SA-CONTRIB-2015-083
* Project: Webform Multiple File Upload [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-March-25
* Security risk: 13/25 ( Moderately Critical)
AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Request Forgery
-------- DESCRIPTION
---------------------------------------------------------
Webform Multiple File Upload module enables you to upload multiple files at
once in webforms.
The module doesn't sufficiently protect some URLs against CSRF. A malicious
user can cause a user with edit access to webforms to delete files by getting
their browser to make a request to a specially-crafted URL.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Webform Multiple File Upload 6.x-1.x versions prior to 6.x-1.3.
* Webform Multiple File Upload 7.x-1.x versions prior to 7.x-1.3.
Drupal core is not affected. If you do not use the contributed Webform
Multiple File Upload [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Webform Multiple File Upload module for Drupal 6.x,
upgrade
to Webform Multiple File Upload 6.x-1.3 [5]
* If you use the Webform Multiple File Upload module for Drupal 7.x,
upgrade
to Webform Multiple File Upload 7.x-1.3 [6]
Also see the Webform Multiple File Upload [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [8] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Jelle Sebreghts [9] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [10] 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/webform_multifile
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/webform_multifile
[5] https://www.drupal.org/node/2459031
[6] https://www.drupal.org/node/2459035
[7] https://www.drupal.org/project/webform_multifile
[8] https://www.drupal.org/user/2301194
[9] https://www.drupal.org/user/829198
[10] https://www.drupal.org/user/2301194
[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/2459315
* Advisory ID: DRUPAL-SA-CONTRIB-2015-082
* Project: Crumbs [1] (third-party module)
* Version: 7.x
* Date: 2015-March-25
* 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 navigation to your webpages colloquially
referred to as "breadcrumbs".
The module doesn't sufficiently sanitize custom HTML separators for
breadcrumbs, thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "Administer Crumbs".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Crumbs 7.x-2.x versions prior to 7.x-2.3
Drupal core is not affected. If you do not use the contributed Crumbs [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Crumbs module for Drupal 7.x, upgrade to Crumbs 7.x-2.3
[5]
Also see the Crumbs [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Colleen Blaho [7]
-------- FIXED BY
------------------------------------------------------------
* Andreas Hennings [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/crumbs
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/crumbs
[5] https://www.drupal.org/node/2458675
[6] https://www.drupal.org/project/crumbs
[7] https://www.drupal.org/user/3042419
[8] https://www.drupal.org/u/donquixote
[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/2459311
* Advisory ID: DRUPAL-SA-CONTRIB-2015-081
* Project: Petition [1] (third-party module)
* Version: 6.x
* Date: 2015-March-25
* 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 Petition module enables you to create petitions which users may sign.
The module doesn't sufficiently sanitize user supplied text in some
administration pages, thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "create petition".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Petition 6.x-1.x versions prior to 6.x-1.3.
Drupal core is not affected. If you do not use the contributed Petition [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Petition module for Drupal 6.x, upgrade to Petition
6.x-1.3
[5]
Also see the Petition [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Sean Robertson [8] the module maintainer
* Pere Orga [9] of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [10] 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/petition
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/petition
[5] https://www.drupal.org/node/2458683
[6] https://www.drupal.org/project/petition
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/7074
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/user/2301194
[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/2455011
* Advisory ID: DRUPAL-SA-CONTRIB-2015-080
* Project: Profile2 Privacy [1] (third-party module)
* Version: 7.x
* Date: 2015-March-18
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Profile2 Privacy module enables you to show or hide parts of a profile2
entity based on pre-configured field sets with a title and description.
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 role
with the permission "Administer Profile2 Privacy Levels".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Profile2 Privacy 7.x-1.x versions prior to 7.x-1.5.
Drupal core is not affected. If you do not use the contributed Profile2
Privacy [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Profile2 Privacy module for Drupal 7.x, upgrade to
Profile2
Privacy 7.x-1.5 [5]
Also see the Profile2 Privacy [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Matt Vance [7] provisional member of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Matt Vance [8] provisional member of the Drupal Security Team
* Jason Yee [9], module maintainer
* Maria Fisher [10], module maintainer
* Greg Knaddison [11] of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* Matt Vance [12] 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 [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] https://www.drupal.org/project/profile2_privacy
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/profile2_privacy
[5] https://www.drupal.org/node/2454383
[6] https://www.drupal.org/project/profile2_privacy
[7] https://www.drupal.org/user/88338
[8] https://www.drupal.org/user/88338
[9] https://www.drupal.org/user/712186
[10] https://www.drupal.org/user/2210776
[11] https://www.drupal.org/user/36762
[12] https://www.drupal.org/user/88338
[13] https://www.drupal.org/contact
[14] https://www.drupal.org/security-team
[15] https://www.drupal.org/writing-secure-code
[16] https://www.drupal.org/security/secure-configuration
[17] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2454909
* Advisory ID: DRUPAL-SA-CONTRIB-2015-079
* Project: Chaos tool suite (ctools) [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-March-18
* Security risk: 13/25 (Moderately Critical)
AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:All [2]
* Vulnerability: Access bypass, Open Redirect
-------- DESCRIPTION
---------------------------------------------------------
This module provides a set of APIs and tools to improve the developer
experience.
.... Access bypass in autocomplete (Drupal 7 only)
Among other many other things, CTools provides an autocomplete callback for
finding entities by their titles or ID.
In CTools version 1.5, additional checks were created to defend against
leaking titles for entities that the user doesn't have access to. However,
certain edge cases were found to leak this private data.
This vulnerability is mitigated by the fact that you must perform the
autocomplete search on custom entities that don't include an access query
tag, or you must know the ID of the entity whose title you are trying to get.
.... Open redirect in confirmation pages (Drupal 6 and 7)
Also, CTools did not sanitize user provided URLs when processing confirmation
delete pages, thereby exposing an open redirect attack vector.
This vulnerability is mitigated by the fact that a module using CTools must
allow for users to insert a malicious external URL that is sent to the
confirmation page.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* CTools 6.x-1.x versions prior to 6.x-1.12.
* CTools 7.x-1.x versions prior to 7.x-1.7.
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 CTools module for Drupal 6.x, upgrade to CTools 6.x-1.12
[5]
* If you use the CTools module for Drupal 7.x, upgrade to CTools 7.x-1.7
[6]
Also see the Chaos tool suite (ctools) [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Richard Thomas [8]
* Pere Orga [9] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Jakob Perry [10], the module maintainer
* Richard Thomas [11]
-------- COORDINATED BY
------------------------------------------------------
* David Snopek [12] of the Drupal Security Team
* Pere Orga [13] 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/ctools
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/ctools
[5] https://www.drupal.org/node/2454885
[6] https://www.drupal.org/node/2454883
[7] https://www.drupal.org/project/ctools
[8] https://www.drupal.org/user/1924680
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/user/45640
[11] https://www.drupal.org/user/1924680
[12] https://www.drupal.org/user/266527
[13] https://www.drupal.org/user/2301194
[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/2454903
* Advisory ID: DRUPAL-SA-CONTRIB-2015-078
* Project: Webform [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-March-18
* Security risk: 11/25 ( Moderately Critical)
AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Default [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Webform is the module for making surveys, petitions, contests, personalized
contact forms, and the like in Drupal.
The module doesn't sufficiently sanitize component names when components are
used to determine the e-mail addresses that may be sent upon webform
submission.
This vulnerability is mitigated by the fact that an attacker must have a role
with permission to create/update nodes with an attached webform and (in
7.x-4.x releases) have the permission "edit webform components".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Webform 6.x-3.x versions prior to 6.x-3.23
* Webform 7.x-3.x versions prior to 7.x-3.23
* Webform 7.x-4.x versions prior to 7.x-4.5
Drupal core is not affected. If you do not use the contributed Webform [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Webform module for Drupal 6.x, upgrade to Webform 6.x-3.23
[5]
* If you use the Webform module for Drupal 7.x, upgrade to Webform 7.x-3.23
[6] or Webform 7.x-4.5 [7], as appropriate.
Also see the Webform [8] project page.
-------- REPORTED BY
---------------------------------------------------------
* Dan Chadwick [9], the module maintainer
-------- FIXED BY
------------------------------------------------------------
* Dan Chadwick [10], the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [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/webform
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/webform
[5] https://www.drupal.org/node/2454055
[6] https://www.drupal.org/node/2454059
[7] https://www.drupal.org/node/2454063
[8] https://www.drupal.org/project/webform
[9] https://www.drupal.org/user/504278
[10] https://www.drupal.org/user/504278
[11] https://www.drupal.org/user/2301194
[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/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