Advertisement






Drupal Content Locking 6.x / 7.x CSRF

CVE Category Price Severity
CVE-2013-3584 CWE-352 $1000 High
Author Risk Exploitation Type Date
Unknown High Remote 2014-02-27
CVSS EPSS EPSSP
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N 0.02192 0.50148

CVSS vector description

Our sensors found this exploit at: http://cxsecurity.com/ascii/WLB-2014020235

Below is a copy:

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


Copyright ©2024 Exploitalert.

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