[<prev] [next>] [day] [month] [year] [list]
Message-ID: <OpenPKG-SA-2007.003@openpkg.com>
Date: Fri, 5 Jan 2007 23:29:18 +0100
From: OpenPKG GmbH <openpkg-noreply@...npkg.com>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2007.003] OpenPKG Security Advisory (drupal)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
____________________________________________________________________________
Publisher Name: OpenPKG GmbH
Publisher Home: http://openpkg.com/
Advisory Id (public): OpenPKG-SA-2007.003
Advisory Type: OpenPKG Security Advisory (SA)
Advisory Directory: http://openpkg.com/go/OpenPKG-SA
Advisory Document: http://openpkg.com/go/OpenPKG-SA-2007.003
Advisory Published: 2007-01-05 23:29 UTC
Issue Id (internal): OpenPKG-SI-20070105.02
Issue First Created: 2007-01-05
Issue Last Modified: 2007-01-05
Issue Revision: 03
____________________________________________________________________________
Subject Name: Drupal
Subject Summary: CMS
Subject Home: http://drupal.org/
Subject Versions: * <= 4.7.4
Vulnerability Id: none
Vulnerability Scope: global (not OpenPKG specific)
Attack Feasibility: run-time
Attack Vector: remote network
Attack Impact: denial of service, privilege escalation
Description:
According to upstream vendor security advisories [0][1], two
vulnerabilities exist in the content management system Drupal [2],
version up to and including 4.7.4.
The first vulnerability exists because a few arguments passed via
URLs are not properly sanitized before display. When an attacker is
able to entice an administrator to follow a specially crafted link,
arbitrary HTML and script code can be injected and executed in the
victim's session. Such an attack may lead to administrator access if
certain conditions are met.
The second vulnerability is related to the way page caching was
implemented. It allows a Denial of Service (DoS) attack. An attacker
has to have the ability to post content on the site. He or she would
then be able to poison the page cache, so that it returns cached
HTTP response code 404 ("page not found") errors for existing pages.
If the page cache is not enabled, your site is not vulnerable. The
vulnerability only affects sites running on top of MySQL, which is
the case in the OpenPKG packaging of Drupal.
References:
[0] http://drupal.org/files/sa-2007-001/advisory.txt
[1] http://drupal.org/files/sa-2007-002/advisory.txt
[2] http://drupal.org/
____________________________________________________________________________
Primary Package Name: drupal
Primary Package Home: http://openpkg.org/go/package/drupal
Corrected Distribution: Corrected Branch: Corrected Package:
OpenPKG Enterprise E1.0-SOLID drupal-4.7.4-E1.0.1
OpenPKG Community 2-STABLE-20061018 drupal-4.7.5-2.20070105
OpenPKG Community 2-STABLE drupal-4.7.5-2.20070105
OpenPKG Community CURRENT drupal-4.7.5-20070105
____________________________________________________________________________
For security reasons, this document was digitally signed with the
OpenPGP public key of the OpenPKG GmbH (public key id 61B7AE34)
which you can download from http://openpkg.com/openpkg.com.pgp
or retrieve from the OpenPGP keyserver at hkp://pgp.openpkg.org/.
Follow the instructions at http://openpkg.com/security/signatures/
for more details on how to verify the integrity of this document.
____________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG GmbH <http://openpkg.com/>
iD8DBQFFntE0ZwQuyWG3rjQRAl5tAJ9j43fMnKFexNP5n91oxbECsG7yxwCfRkwp
cegWv+RWvCjZmKIxb8fj+rQ=
=U78P
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists