VuXML ID | Description |
be927298-6f97-11de-b444-001372fd0af2 | drupal -- multiple vulnerabilities
The Drupal Security Team reports:
Cross-site scripting
The Forum module does not correctly handle certain arguments
obtained from the URL. By enticing a suitably privileged user
to visit a specially crafted URL, a malicious user is able to
insert arbitrary HTML and script code into forum pages. Such a
cross-site scripting attack may lead to the malicious user
gaining administrative access. Wikipedia has more information
about cross-site scripting (XSS).
User signatures have no separate input format, they use the
format of the comment with which they are displayed. A user
will no longer be able to edit a comment when an administrator
changes the comment's input format to a format that is not
accessible to the user. However they will still be able to
modify their signature, which will then be processed by the new
input format.
If the new format is very permissive, via their signature, the
user may be able to insert arbitrary HTML and script code into
pages or, when the PHP filter is enabled for the new format,
execute PHP code. This issue affects Drupal 6.x only.
When an anonymous user fails to login due to mistyping his
username or password, and the page he is on contains a sortable
table, the (incorrect) username and password are included in
links on the table. If the user visits these links the password
may then be leaked to external sites via the HTTP referer.
In addition, if the anonymous user is enticed to visit the site
via a specially crafted URL while the Drupal page cache is
enabled, a malicious user might be able to retrieve the
(incorrect) username and password from the page cache.
Discovery 2009-07-01 Entry 2009-07-13 Modified 2010-05-02 drupal5
< 5.19
drupal6
< 6.13
CVE-2009-2372
CVE-2009-2374
CVE-2009-2373
http://drupal.org/node/507572
http://secunia.com/advisories/35681
|
751823d4-f189-11de-9344-00248c9b4be7 | drupal -- multiple cross-site scripting
Drupal Team reports:
The Contact module does not correctly handle certain user input
when displaying category information. Users privileged to create
contact categories can insert arbitrary HTML and script code into the
contact module administration page. Such a cross-site scripting attack
may lead to the malicious user gaining administrative access.
The Menu module does not correctly handle certain user input when
displaying the menu administration overview. Users privileged to
create new menus can insert arbitrary HTML and script code into the
menu module administration page. Such a cross-site scripting attack
may lead to the malicious user gaining administrative access.
Discovery 2009-12-16 Entry 2009-12-25 Modified 2010-05-02 drupal5
< 5.21
drupal6
< 6.15
CVE-2009-4370
http://drupal.org/node/661586
|
609c790e-ce0a-11dd-a721-0030843d3802 | drupal -- multiple vulnerabilities
The Drupal Project reports:
The update system is vulnerable to Cross site request forgeries.
Malicious users may cause the superuser (user 1) to execute old
updates that may damage the database.
When an input format is deleted, not all existing content on a site
is updated to reflect this deletion. Such content is then displayed
unfiltered. This may lead to cross site scripting attacks when harmful
tags are no longer stripped from 'malicious' content that was posted
earlier.
Discovery 2008-12-11 Entry 2008-12-19 Modified 2010-05-02 drupal5
< 5.14
drupal6
< 6.8
CVE-2008-6533
http://drupal.org/node/345441
http://secunia.com/advisories/33112/
|
a6605f4b-4067-11de-b444-001372fd0af2 | drupal -- cross-site scripting
The Drupal Security Team reports:
When outputting user-supplied data Drupal strips potentially
dangerous HTML attributes and tags or escapes characters which
have a special meaning in HTML. This output filtering secures the
site against cross site scripting attacks via user input.
Certain byte sequences that are valid in the UTF-8 specification
are potentially dangerous when interpreted as UTF-7. Internet
Explorer 6 and 7 may decode these characters as UTF-7 if they
appear before the tag that
specifies the page content as UTF-8, despite the fact that Drupal
also sends a real HTTP header specifying the content as UTF-8.
This enables attackers to execute cross site scripting attacks
with UTF-7. SA-CORE-2009-005 - Drupal core - Cross site scripting
contained an incomplete fix for the issue. HTML exports of books
are still vulnerable, which means that anyone with edit
permissions for pages in outlines is able to insert arbitrary HTML
and script code in these exports.
Additionally, the taxonomy module allows users with the
'administer taxonomy' permission to inject arbitrary HTML and
script code in the help text of any vocabulary.
Discovery 2009-05-13 Entry 2009-05-14 Modified 2009-05-16 drupal5
< 5.18
drupal6
< 6.12
http://drupal.org/node/461886
http://secunia.com/advisories/35045
|
6d85dc62-f2bd-11dd-9f55-0030843d3802 | drupal -- multiple vulnerabilities
Drupal Team reports:
The Content Translation module for Drupal 6.x enables users to make
a translation of an existing item of content (a node). In that proces
the existing node's content is copied into the new node's submission
form.
The module contains a flaw that allows a user with the 'translate
content' permission to potentially bypass normal viewing access
restrictions, for example allowing the user to see the content of
unpublished nodes even if they do not have permission to view
unpublished nodes.
When user profile pictures are enabled, the default user profile
validation function will be bypassed, possibly allowing invalid user
names or e-mail addresses to be submitted.
Discovery 2009-01-14 Entry 2009-02-04 drupal5
< 5.15
drupal6
< 6.9
http://drupal.org/node/358957
http://secunia.com/advisories/33550/
http://secunia.com/advisories/33500/
http://secunia.com/advisories/33542/
|
b3531fe1-2b03-11df-b6db-00248c9b4be7 | drupal -- multiple vulnerabilities
Drupal Team reports:
A user-supplied value is directly output during installation
allowing a malicious user to craft a URL and perform a cross-site
scripting attack. The exploit can only be conducted on sites not yet
installed.
The API function drupal_goto() is susceptible to a phishing attack.
An attacker could formulate a redirect in a way that gets the Drupal
site to send the user to an arbitrarily provided URL. No user
submitted data will be sent to that URL.
Locale module and dependent contributed modules do not sanitize the
display of language codes, native and English language names properly.
While these usually come from a preselected list, arbitrary
administrator input is allowed. This vulnerability is mitigated by the
fact that the attacker must have a role with the 'administer
languages' permission.
Under certain circumstances, a user with an open session that is
blocked can maintain his/her session on the Drupal site, despite being
blocked.
Discovery 2010-03-03 Entry 2010-03-08 drupal5
< 5.22
drupal6
< 6.16
http://drupal.org/node/731710
|
bad1b090-a7ca-11de-873f-0030843d3802 | drupal -- multiple vulnerabilities
Drupal Team reports:
The core OpenID module does not correctly implement Form API for
the form that allows one to link user accounts with OpenID
identifiers. A malicious user is therefore able to use cross site
request forgeries to add attacker controlled OpenID identities to
existing accounts. These OpenID identities can then be used to gain
access to the affected accounts.
The OpenID module is not a compliant implementation of the OpenID
Authentication 2.0 specification. An implementation error allows a
user to access the account of another user when they share the same
OpenID 2.0 provider.
File uploads with certain extensions are not correctly processed by
the File API. This may lead to the creation of files that are
executable by Apache. The .htaccess that is saved into the files
directory by Drupal should normally prevent execution. The files are
only executable when the server is configured to ignore the directives
in the .htaccess file.
Drupal doesn't regenerate the session ID when an anonymous user
follows the one time login link used to confirm email addresses and
reset forgotten passwords. This enables a malicious user to fix and
reuse the session id of a victim under certain circumstances.
Discovery 2009-09-17 Entry 2009-09-22 drupal5
< 5.20
drupal6
< 6.14
http://drupal.org/node/579482
http://secunia.com/advisories/36787/
http://secunia.com/advisories/36786/
http://secunia.com/advisories/36781/
http://secunia.com/advisories/36776/
http://secunia.com/advisories/36785/
|
7a1ab8d4-35c1-11de-9672-0030843d3802 | drupal -- cross site scripting
Drupal Security Team reports:
When outputting user-supplied data Drupal strips potentially
dangerous HTML attributes and tags or escapes characters which have a
special meaning in HTML. This output filtering secures the site
against cross site scripting attacks via user input.
Certain byte sequences that are valid in the UTF-8 specification
are potentially dangerous when interpreted as UTF-7. Internet Explorer
6 and 7 may decode these characters as UTF-7 if they appear before the
meta http-equiv="Content-Type" tag that specifies the page content
as UTF-8, despite the fact that Drupal also sends a real HTTP header
specifying the content as UTF-8. This behaviour enables malicious
users to insert and execute Javascript in the context of the website
if site visitors are allowed to post content.
In addition, Drupal core also has a very limited information
disclosure vulnerability under very specific conditions. If a user is
tricked into visiting the site via a specially crafted URL and then
submits a form (such as the search box) from that page, the
information in their form submission may be directed to a third-party
site determined by the URL and thus disclosed to the third party. The
third party site may then execute a CSRF attack against the submitted
form.
Discovery 2009-04-30 Entry 2009-04-30 Modified 2010-05-02 drupal5
< 5.17
drupal6
< 6.11
CVE-2009-1575
CVE-2009-1576
http://drupal.org/node/449078
|