Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2014.0802
A vulnerabilitiy has been identified in Drupal core
22 May 2014
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Drupal
Publisher: Drupal
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Access Confidential Data -- Existing Account
Resolution: Mitigation
Original Bulletin:
https://drupal.org/PSA-2014-002
- --------------------------BEGIN INCLUDED TEXT--------------------
View online:
* Advisory ID: DRUPAL-PSA-2014-002
* Project: Drupal core [1]
* Version: 6.x, 7.x
* Date: 2014-May-21
* Security risk: Not critical [2]
* Exploitable from: Remote
* Vulnerability: Information Disclosure
- -------- DESCRIPTION---------------------------------------------------------
This is a public service announcement regarding the "access site reports"
permission (labeled as "View site reports" in the Drupal 7 administrative
interface) provided by Drupal 6 and 7 core.
This permission allows users to see logs (for example, those provided by the
core Database Logging module) and other reports via the administrative
interface of a Drupal site. Due to the nature of the data logged by various
core and contributed modules, users with this permission can see information
in the logs that they otherwise may not have access to (for example, the
titles of nodes that are restricted by node access).
As such:
* This permission should be granted to trusted site administrators only. It
is now listed as an advanced permission at
https://drupal.org/security-advisory-policy [3], and a future release of
Drupal 7 core will mark it as restricted on the permissions page as well.
* Developers may freely use Drupal's watchdog() function to log relevant
information about the actions they are performing (without worrying about
minor information disclosure or access bypass issues). However, care
should still be taken to only log what is necessary. For example,
logging extremely sensitive information such as plain-text user passwords
(see SA-CONTRIB-2010-091 [4]) would still be considered a security issue
because plain-text passwords should never be saved or displayed anywhere
on the site.
- -------- CVE IDENTIFIER(S) ISSUED--------------------------------------------
* /A CVE identifier [5] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
- -------- VERSIONS AFFECTED---------------------------------------------------
All versions of Drupal 6 and Drupal 7 core.
- -------- SOLUTION------------------------------------------------------------
Only grant trusted site administrators the "access site reports"/"View site
reports" permission.
Also see the Drupal core [6] project page.
- -------- 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/drupal
[2] http://drupal.org/security-team/risk-levels
[3] https://drupal.org/security-advisory-policy
[4] https://drupal.org/node/912412
[5] http://cve.mitre.org/
[6] http://drupal.org/project/drupal
[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
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBU31r/RLndAQH1ShLAQJ++g//eUx8MwXeYOiZHKMtNICNnaoAEjR6jgEA
1jXxDs6oRkqAdVLSBuwtR619m0X5+n+XfSvr+H//zzFRbs2zukjQyoCseYyswhFc
4U/DLSvaVPD/y2ud4dn0NsqATvh3zhKyCsHHR2bwh9l+SEgzc4MgSF5/00dmvDTv
UJXSZrXWjqyOR/rMzFCBja/08WPWgFBTUwsA8RemwmxsgZe8YaqtVAseU76iPPSY
RHUIWIfRroOy7ALr4iW1TQcfl8pAPglCuprye3gXZR70FcSFpbUTgW8YBVd+zaOJ
l3tWCp+OS0zHD+aGixd+App62la9KywjMwKQv+OZpCEp1QNuamww4tkgoN+hJLcJ
6TW8UePEEaEXqRN9Pzul3Qw2VDZF0kMo2rzx9Ty9qi7Wwm+4QOvi+UnjGN8zDFGx
Nd5qhygsUHZJUxm7agS7X/Q2FmWdyD/5YJOmJUzTzo1uQ2EZMFHb9P2dTVURzhZZ
YRqGPjk9Oa37tdgSfx0lzJZZoNjvW7aU+ISspxmS56kjIaJ2MU4rS/lsL7PM6C1t
+g7oc89muK3NcgKXEPvAaU3rN1/6q32hfcTFG1viRcGXSU8OysL3cnDUVQsXZlED
6QJSH6+cLaaWCiqOehy0mNU+BxzyZBeFaYaseePnShuGCW9TcpcqRR3vhGg57pO1
tjOc99Jqd3o=
=QlVt
-----END PGP SIGNATURE-----