The form API in Drupal 6.x before 6.29 and 7.x before 7.24, when used with unspecified third-party modules, performs form validation even when CSRF validation has failed, which might allow remote attackers to trigger application-specific impacts such as arbitrary code execution via application-specific vectors.

The version of Drupal installed on the remote server is 7.x prior to 7.24, and is affected by the following vulnerabilities :

 - A flaw exists in unspecified configurations for Apache Web Servers that can cause the .htaccess file that would normally protect against code execution to be ignored. This may allow a remote attacker to more easily execute code on a system that is vulnerable to malicious file uploads.
 - A flaw exists in the 'drupal_valid_token()' function that is triggered when the TRUE value is returned for invalid security tokens if the caller fails to ensure that the token is a string. This may allow a remote attacker to bypass security token validation.
 - A flaw exists that allows a stored cross-site scripting (XSS) attack. This flaw exists because the application does not validate input passed via the image field description in the image module. This may allow an attacker to create a specially crafted request that would execute arbitrary script code in a user's browser within the trust relationship between their browser and the server.
 - A flaw exists that allows a reflected XSS attack. This flaw exists because the application does not validate certain unspecified input related to the color module before returning it to the user. This may allow an attacker to create a specially crafted request that would execute arbitrary script code in a user's browser within the trust relationship between their browser and the server.
 - A flaw exists in the overlay module that is due to the module failing to sanitize URLs before administrative pages are layered over current pages instead of replacing them. This could allow a user to create a specially crafted URL, that if clicked, would redirect a victim from the intended legitimate web site to an arbitrary web site of the attacker's choosing. Such attacks are useful as the crafted URL initially appears to be a web page of a trusted site. This could be leveraged to direct an unsuspecting user to a web page containing attacks that target client side software such as a web browser or document rendering programs.
 - A flaw exists in the form API that is due to the program failing to properly implement CSRF protection when a third-party module uses form validation callbacks with potentially unsafe operations. This may allow a context-dependent attacker to bypass protections against CSRF attacks.

Multiple vulnerabilities have been discovered in Drupal, a fully-featured content management framework: vulnerabilities due to optimistic cross-site request forgery protection, insecure pseudo random number generation, code execution and incorrect security token validation.

In order to avoid the remote code execution vulnerability, it is recommended to create a .htaccess file (or an equivalent configuration directive in case you are not using Apache to serve your Drupal sites) in each of your sites' 'files' directories (both public and private, in case you have both configured).

Please refer to the NEWS file provided with this update and the upstream advisory at drupal.org/SA-CORE-2013-003 for further information.

- Update to upstream 6.29 release for security fixes

    - Upstream changelog for this release is available at       https://drupal.org/drupal-6.29-release-notes

    - SA-CORE-2013-003 - Drupal core - Multiple       vulnerabilities - http://drupal.org/SA-CORE-2013-003

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

- Update to upstream 7.24 release for security fixes

    - Upstream changelog for this release is available at       https://drupal.org/drupal-7.24-release-notes

    - SA-CORE-2013-003 - Drupal core - Multiple       vulnerabilities - http://drupal.org/SA-CORE-2013-003

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote web server is running a version of Drupal that is 7.x prior to 7.24. It is, therefore, potentially affected by multiple vulnerabilities :

  - An error exists related to the HTML form API and     validation callbacks as used by third-party modules     that could allow an attacker to bypass the cross-site     request forgery protections. (CVE-2013-6385)

  - An error exists in the function mt_rand(), used for     pseudorandom number generation, that could allow an     attacker to obtain seeds through brute-force attacks.
    (CVE-2013-6386)

  - A user-input validation error exists in the 'image'     module that could allow persistent cross-site scripting     attacks via the image field description parameter.
    (CVE-2013-6387)

  - A user-input validation error exists in the 'color'     module that could allow cross-site scripting attacks     via unspecified inputs. (CVE-2013-6388)

  - An error exists related to admin pages and overlays     that could allow a user to be tricked into making     requests to malicious websites via an arbitrary     redirect. (CVE-2013-6389)

  - On Apache web servers containing application code that     does not protect against the execution of uploaded     files, it may be possible to upload arbitrary PHP files     and cause them to execute. Note that if the intended     remediation is an upgrade and the server is an Apache     server, a manual fix is required. (BID 63845)

  - An error exists in the function drupal_valid_token()     that could allow it to validate invalid tokens, thus     allowing a security bypass. Note that an attacker must     be able to cause a non-string value to be passed to the     function for a successful attack. (BID 63849)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote web server is running a version of Drupal that is 6.x prior to 6.29. It is, therefore, potentially affected by multiple vulnerabilities :

  - An error exists related to the HTML form API and     validation callbacks as used by third-party modules     that could allow an attacker to bypass the cross-site     request forgery protections. (CVE-2013-6385)

  - An error exists in the function mt_rand(), used for     pseudorandom number generation, that could allow an     attacker to obtain seeds through brute-force attacks.
    (CVE-2013-6386)

  - On Apache web servers containing application code that     does not protect against the execution of uploaded     files, it may be possible to upload arbitrary PHP files     and cause them to execute. Note that if the intended     remediation is an upgrade and the server is an Apache     server, a manual fix is required. (BID 63845)

  - An error exists in the function drupal_valid_token()     that could allow it to validate invalid tokens, thus     allowing a security bypass. Note that an attacker must     be able to cause a non-string value to be passed to the     function for a successful attack. (BID 63849)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Multiple security issues was identified and fixed in drupal :

Drupal core's Image module allows for the on-demand generation of image derivatives. This capability can be abused by requesting a large number of new derivatives which can fill up the server disk space, and which can cause a very high CPU load. Either of these effects may lead to the site becoming unavailable or unresponsive (CVE-2013-0316).

Drupal's form API has built-in cross-site request forgery (CSRF) validation, and also allows any module to perform its own validation on the form. In certain common cases, form validation functions may execute unsafe operations (CVE-2013-6385).

Drupal core directly used the mt_rand() pseudorandom number generator for generating security related strings used in several core modules.
It was found that brute force tools could determine the seeds making these strings predictable under certain circumstances (CVE-2013-6386).

Image field descriptions are not properly sanitized before they are printed to HTML, thereby exposing a cross-site scripting vulnerability (CVE-2013-6387).

A cross-site scripting vulnerability was found in the Color module. A malicious attacker could trick an authenticated administrative user into visiting a page containing specific JavaScript that could lead to a reflected cross-site scripting attack via JavaScript execution in CSS (CVE-2013-6388).

The Overlay module displays administrative pages as a layer over the current page (using JavaScript), rather than replacing the page in the browser window. The Overlay module did not sufficiently validate URLs prior to displaying their contents, leading to an open redirect vulnerability (CVE-2013-6389).

The updated packages has been upgraded to the 7.24 version which is unaffected by these security flaws.

Update :

Additional apache ACL restrictions has been added to fully conform to the SA-CORE-2013-003 advisory.

Multiple vulnerabilities have been discovered in Drupal, a fully-featured content management framework: Cross-site request forgery, insecure pseudo random number generation, code execution, incorrect security token validation and cross-site scripting.

In order to avoid the remote code execution vulnerability, it is recommended to create a .htaccess file (or an equivalent configuration directive in case you are not using Apache to serve your Drupal sites) in each of your sites' 'files' directories (both public and private, in case you have both configured).

Please refer to the NEWS file provided with this update and the upstream advisory at drupal.org/SA-CORE-2013-003 for further information.

ID	Name	Product	Family	Severity
9727	Drupal 7.x < 7.24 Multiple Vulnerabilities	Nessus Network Monitor	CGI	medium
71764	Debian DSA-2828-1 : drupal6 - several vulnerabilities	Nessus	Debian Local Security Checks	medium
71408	Fedora 20 : drupal6-6.29-1.fc20 (2013-22352)	Nessus	Fedora Local Security Checks	medium
71404	Fedora 20 : drupal7-7.24-1.fc20 (2013-21956)	Nessus	Fedora Local Security Checks	medium
71358	Fedora 19 : drupal6-6.29-1.fc19 (2013-22507)	Nessus	Fedora Local Security Checks	medium
71148	Fedora 19 : drupal7-7.24-1.fc19 (2013-21844)	Nessus	Fedora Local Security Checks	medium
71145	Drupal 7.x < 7.24 Multiple Vulnerabilities	Nessus	CGI abuses	medium
71144	Drupal 6.x < 6.29 Multiple Vulnerabilities	Nessus	CGI abuses	medium
71101	Mandriva Linux Security Advisory : drupal (MDVSA-2013:287-1)	Nessus	Mandriva Local Security Checks	medium
71098	Debian DSA-2804-1 : drupal7 - several vulnerabilities	Nessus	Debian Local Security Checks	medium

Detections

Analytics

CVE-2013-6385

high

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium