View online: https://www.drupal.org/node/2403343
* Advisory ID: DRUPAL-SA-CONTRIB-2015-003
* Project: PHPlist Integration Module [1] (third-party module)
* Version: 6.x
* Date: 2015-January-07
* Security risk: 13/25 ( Moderately Critical)
AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: SQL Injection
-------- DESCRIPTION
---------------------------------------------------------
The PHPlist Integration module provides an integration between a Drupal
website and phpList newsletter manager. The module provides two main
features: user sync and sending a node as a newsletter.
The module introduces a SQL Injection vulnerability to the phpList database.
The Drupal database is not affected.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "administer PHPlist".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* PHPlist Integration Module 6.x-1.x versions prior to 6.x-1.7.
Drupal core is not affected. If you do not use the contributed PHPlist
Integration Module [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the PHPlist Integration Module for Drupal 6.x, upgrade to
PHPlist Integration Module 6.x-1.7 [5]
Also see the PHPlist Integration Module [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] provisional member of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Tarek Djebali [8] the module maintainer
* Pere Orga [9] provisional member of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [10] provisional member of the Drupal Security Team
* Klaus Purer [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/phplist
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/phplist
[5] https://www.drupal.org/node/2402517
[6] https://www.drupal.org/project/phplist
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/745218
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/user/2301194
[11] https://www.drupal.org/u/klausi
[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/2403333
* Advisory ID: DRUPAL-SA-CONTRIB-2015-002
* Project: Course [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-January-07
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Course module enables you to create e-learning courses with any number of
requirements for completion.
The module doesn't sufficiently filter node title displays when being used in
a course.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission to create course content.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Course 7.x-1.x versions prior to 7.x-1.4
* Course 6.x-1.x versions prior to 6.x-1.2
Drupal core is not affected. If you do not use the contributed Course [4]
module,
there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Course module for Drupal 7.x, upgrade to Course 7.x-1.4
[5]
* If you use the Course module for Drupal 6.x, upgrade to Course 6.x-1.2
[6]
Also see the Course [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [8] provisional member of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Pere Orga [9] provisional member of the Drupal Security Team
* Devin Zuczek [10] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [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/course
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/course
[5] https://www.drupal.org/node/2403305
[6] https://www.drupal.org/node/2403309
[7] https://www.drupal.org/project/course
[8] https://www.drupal.org/user/2301194
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/user/701754
[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/node/2403313
* Advisory ID: DRUPAL-SA-CONTRIB-2015-001
* Project: OPAC [1] (third-party module)
* Version: 7.x
* Date: 2015-January-07
* 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
---------------------------------------------------------
OPAC module enables you to create mappings between node fields and ILS record
fields.
The module doesn't ask for confirmation when removing a mapping, leaving this
operation vulnerable to cross-site request forgery (CSRF) attacks.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance
with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* OPAC 7.x-2.x versions prior to 7.x-2.3.
Drupal core is not affected. If you do not use the contributed OPAC [4]
module,
there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the OPAC module 7.x-2.0, upgrade to OPAC 7.x-2.3 [5]
Also see the OPAC [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Pere Orga [7] provisional member of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Julian Maurice [8] the module maintainer
* Pere Orga [9] provisional member of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [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/opac
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/opac
[5] https://www.drupal.org/node/2402393
[6] https://www.drupal.org/project/opac
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/user/2221570
[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