View online: https://drupal.org/node/2205807
* Advisory ID: DRUPAL-SA-CONTRIB-2014-024
* Project: Content locking (anti-concurrent editing) [1] (third-party
module)
* Version: 6.x, 7.x
* Date: 2014-February-26
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Request Forgery
-------- DESCRIPTION
---------------------------------------------------------
This module prevents people from editing the same content at the same time.
It adds a locking layer to nodes. It does not protect from CSRF.
-------- 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 6.x Versions
* All 7.x Versions
Drupal core is not affected. If you do not use the contributed Content
locking (anti-concurrent editing) [4] module, there is nothing you need to
do.
-------- SOLUTION
------------------------------------------------------------
Uninstall the module, it is no longer maintained .
Also see the Content locking (anti-concurrent editing) [5] project page.
-------- REPORTED BY
---------------------------------------------------------
* Eugen Mayer [6]
-------- FIXED BY
------------------------------------------------------------
There is no fix for this issue.
-------- 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 [7].
Learn more about the Drupal Security team and their policies [8], writing
secure code for Drupal [9], and securing your site [10].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [11]
[1] http://drupal.org/project/content_lock
[2] http://drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://drupal.org/project/content_lock
[5] http://drupal.org/project/content_lock
[6] https://drupal.org/user/108406
[7] http://drupal.org/contact
[8] http://drupal.org/security-team
[9] http://drupal.org/writing-secure-code
[10] http://drupal.org/security/secure-configuration
[11] https://twitter.com/drupalsecurity
_______________________________________________
Security-news mailing list
Security-news@drupal.org
Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
* Advisory ID: DRUPAL-SA-CONTRIB-2014-024
* Project: Content locking (anti-concurrent editing) [1] (third-party
module)
* Version: 6.x, 7.x
* Date: 2014-February-26
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Request Forgery
-------- DESCRIPTION
---------------------------------------------------------
This module prevents people from editing the same content at the same time.
It adds a locking layer to nodes. It does not protect from CSRF.
-------- 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 6.x Versions
* All 7.x Versions
Drupal core is not affected. If you do not use the contributed Content
locking (anti-concurrent editing) [4] module, there is nothing you need to
do.
-------- SOLUTION
------------------------------------------------------------
Uninstall the module, it is no longer maintained .
Also see the Content locking (anti-concurrent editing) [5] project page.
-------- REPORTED BY
---------------------------------------------------------
* Eugen Mayer [6]
-------- FIXED BY
------------------------------------------------------------
There is no fix for this issue.
-------- 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 [7].
Learn more about the Drupal Security team and their policies [8], writing
secure code for Drupal [9], and securing your site [10].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [11]
[1] http://drupal.org/project/content_lock
[2] http://drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://drupal.org/project/content_lock
[5] http://drupal.org/project/content_lock
[6] https://drupal.org/user/108406
[7] http://drupal.org/contact
[8] http://drupal.org/security-team
[9] http://drupal.org/writing-secure-code
[10] http://drupal.org/security/secure-configuration
[11] https://twitter.com/drupalsecurity
_______________________________________________
Security-news mailing list
Security-news@drupal.org
Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/