VuXML ID | Description |
e00ed3d9-1c27-11e9-a257-000ffec0b3e1 | drupal -- Drupal core - Arbitrary PHP code execution
Drupal Security Team reports:
A remote code execution vulnerability exists in PHP's built-in
phar stream wrapper when performing file operations on an untrusted phar:// URI.
Some Drupal code (core, contrib, and custom) may be performing file operations on
insufficiently validated user input, thereby being exposed to this vulnerability.
This vulnerability is mitigated by the fact that such code paths typically require
access to an administrative permission or an atypical configuration.
Discovery 2019-01-16 Entry 2019-01-19 drupal7
< 7.63
drupal8
< 8.6.7
https://www.drupal.org/SA-CORE-2018-006
|
b51d5391-bb76-11ea-9172-4c72b94353b5 | drupal -- Multiple Vulnerabilities
Drupal Security Team reports:
The Drupal core Form API does not properly handle certain form input
from cross-site requests, which can lead to other vulnerabilities.
Discovery 2020-06-17 Entry 2020-07-01 drupal7
< 7.72
https://www.drupal.org/sa-core-2020-004
|
2bad8b5d-66fb-11e9-9815-78acc0a3b880 | drupal -- Drupal core - Moderately critical
Drupal Security Team reports:
CVE-2019-10909: Escape validation messages in the PHP templating engine.
CVE-2019-10910: Check service IDs are valid.
CVE-2019-10911: Add a separator in the remember me cookie hash.
jQuery 3.4.0 includes a fix for some unintended behavior when using
jQuery.extend(true, {}, ...). If an unsanitized source object contained
an enumerable __proto__ property, it could extend the native Object.prototype.
This fix is included in jQuery 3.4.0, but patch diffs exist to patch previous
jQuery versions.
It's possible that this vulnerability is exploitable with some Drupal modules.
As a precaution, this Drupal security release backports the fix to jQuery.extend(),
without making any other changes to the jQuery version that is included in
Drupal core (3.2.1 for Drupal 8 and 1.4.4 for Drupal 7) or running on the site
via some other module such as jQuery Update.
Discovery 2019-04-17 Entry 2019-04-25 drupal7
< 7.66
drupal8
< 8.6.15
https://www.drupal.org/SA-CORE-2019-005
https://www.drupal.org/SA-CORE-2019-006
|
94d63fd7-508b-11e9-9ba0-4c72b94353b5 | drupal -- Drupal core - Moderately critical - Cross Site Scripting
Drupal Security Team reports:
Under certain circumstances the File module/subsystem allows a malicious
user to upload a file that can trigger a cross-site scripting (XSS) vulnerability.
Discovery 2019-03-20 Entry 2019-03-27 Modified 2019-03-28 drupal7
< 7.65
drupal8
< 8.6.13
https://www.drupal.org/project/drupal/releases/8.6.13
https://www.drupal.org/project/drupal/releases/7.65
https://www.drupal.org/SA-CORE-2019-004
CVE-2019-6341
|
f70ab05e-be06-11eb-b983-000c294bb613 | drupal7 -- fix possible CSS
Drupal Security team reports:
Drupal core's sanitization API fails to properly filter
cross-site scripting under certain circumstances.
Not all sites and users are affected, but configuration
changes to prevent the exploit might be impractical
and will vary between sites. Therefore, we recommend
all sites update to this release as soon as
possible.
Discovery 2021-04-21 Entry 2021-06-06 drupal7
gt 7.0 lt 7.80
CVE-2020-13672
|
57580fcc-1a61-11e8-97e0-00e04c1ea73d | drupal -- Drupal Core - Multiple Vulnerabilities
Drupal Security Team reports:
CVE-2017-6926: Comment reply form allows access to restricted content
CVE-2017-6927: JavaScript cross-site scripting prevention is incomplete
CVE-2017-6928: Private file access bypass - Moderately Critical
CVE-2017-6929: jQuery vulnerability with untrusted domains - Moderately Critical
CVE-2017-6930: Language fallback can be incorrect on multilingual sites with node access restrictions
CVE-2017-6931: Settings Tray access bypass
CVE-2017-6932: External link injection on 404 pages when linking to the current page
Discovery 2018-02-21 Entry 2018-02-25 drupal7
< 7.56
drupal8
< 8.4.4
CVE-2017-6928
CVE-2017-6926
CVE-2017-6927
CVE-2017-6929
CVE-2017-6930
CVE-2017-6931
CVE-2017-6932
|
95d9d986-1078-11eb-ab74-4c72b94353b5 | drupal -- Multiple Vulnerabilities
Drupal Security Team reports:
The Drupal AJAX API does not disable JSONP by default, which can
lead to cross-site scripting.
Discovery 2020-09-16 Entry 2020-10-17 drupal7
< 7.72
https://www.drupal.org/sa-core-2020-007
|
c5ec57a9-9c2b-11ea-82b8-4c72b94353b5 | drupal -- Multiple Vulnerabilities
Drupal Security Team reports:
The jQuery project released version 3.5.0, and as part of that,
disclosed two security vulnerabilities that affect all prior versions.
As mentioned in the jQuery blog, both are: ... Security issues in
jQuerys DOM manipulation methods, as in .html(), .append(), and the others.
Security advisories for both of these issues have been published on GitHub.
Drupal 7 has an Open Redirect vulnerability.
For example, a user could be tricked into visiting a specially crafted link
which would redirect them to an arbitrary external URL. The vulnerability is
caused by insufficient validation of the destination query parameter in the
drupal_goto() function.
Discovery 2020-05-20 Entry 2020-05-22 drupal7
< 7.70
drupal8
< 8.8.6
https://www.drupal.org/sa-core-2020-002
https://www.drupal.org/sa-core-2020-003
|
8db24888-b2f5-11e6-8153-00248c0c745d | Drupal Code -- Multiple Vulnerabilities
The Drupal development team reports:
Inconsistent name for term access query (Less critical - Drupal
7 and Drupal 8)
Drupal provides a mechanism to alter database SELECT queries before
they are executed. Contributed and custom modules may use this
mechanism to restrict access to certain entities by implementing
hook_query_alter() or hook_query_TAG_alter() in order to add
additional conditions. Queries can be distinguished by means of
query tags. As the documentation on EntityFieldQuery::addTag()
suggests, access-tags on entity queries normally follow the form
ENTITY_TYPE_access (e.g. node_access). However, the taxonomy
module's access query tag predated this system and used term_access
as the query tag instead of taxonomy_term_access.
As a result, before this security release modules wishing to
restrict access to taxonomy terms may have implemented an
unsupported tag, or needed to look for both tags (term_access and
taxonomy_term_access) in order to be compatible with queries
generated both by Drupal core as well as those generated by
contributed modules like Entity Reference. Otherwise information
on taxonomy terms might have been disclosed to unprivileged users.
Incorrect cache context on password reset page (Less critical -
Drupal 8)
The user password reset form does not specify a proper cache
context, which can lead to cache poisoning and unwanted content on
the page.
Confirmation forms allow external URLs to be injected (Moderately
critical - Drupal 7)
Under certain circumstances, malicious users could construct a URL
to a confirmation form that would trick users into being redirected
to a 3rd party website after interacting with the form, thereby
exposing the users to potential social engineering attacks.
Denial of service via transliterate mechanism (Moderately critical
- Drupal 8)
A specially crafted URL can cause a denial of service via the
transliterate mechanism.
Discovery 2016-11-16 Entry 2016-11-25 Modified 2016-11-27 drupal7
ge 7.0 lt 7.52
drupal8
ge 8.0.0 lt 8.2.3
CVE-2016-9449
CVE-2016-9450
CVE-2016-9451
CVE-2016-9452
|
140a14b5-d615-11e8-b3cb-00e04c1ea73d | drupal -- Drupal Core - Multiple Vulnerabilities
Drupal Security Team reports:
he path module allows users with the 'administer paths' to create pretty URLs
for content. In certain circumstances the user can enter a particular path that
triggers an open redirect to a malicious url.The issue is mitigated by the fact
that the user needs the administer paths permission to exploit.
When sending email some variables were not being sanitized for shell arguments,
which could lead to remote code execution.
Discovery 2018-10-17 Entry 2018-10-22 Modified 2018-11-04 drupal7
< 7.60
drupal8
< 8.6.2
https://www.drupal.org/SA-CORE-2018-006
|
a9e466e8-4144-11e8-a292-00e04c1ea73d | drupal -- Drupal Core - Multiple Vulnerabilities
Drupal Security Team reports:
CVE-2018-7600: Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6,
and 8.5.x before 8.5.1 allows remote attackers to execute arbitrary code because
of an issue affecting multiple subsystems with default or common module configurations.
Discovery 2018-03-13 Entry 2018-04-16 drupal7
< 7.57
CVE-2018-7600
|
3da0352f-2397-11ea-966e-000ffec0b3e1 | drupal -- Drupal Core - Multiple Vulnerabilities
Drupal Security Team reports:
A visit to install.php can cause cached data to become corrupted.
This could cause a site to be impaired until caches are rebuilt.
Drupal 8 core's file_save_upload() function does not strip the
leading and trailing dot ('.') from filenames, like Drupal 7 did.
Users with the ability to upload files with any extension in
conjunction with contributed modules may be able to use this to
upload system files such as .htaccess in order to bypass protections
afforded by Drupal's default .htaccess file. After this fix,
file_save_upload() now trims leading and trailing dots from filenames.
The Media Library module has a security vulnerability whereby it
doesn't sufficiently restrict access to media items in certain
configurations.
The Drupal project uses the third-party library Archive_Tar, which
has released a security-related feature that impacts some Drupal
configurations. Multiple vulnerabilities are possible if Drupal is
configured to allow .tar, .tar.gz, .bz2 or .tlz file uploads and
processes them. The latest versions of Drupal update Archive_Tar to
1.4.9 to mitigate the file processing vulnerabilities.
Discovery 2019-12-18 Entry 2019-12-21 drupal7
< 7.69
drupal8
< 8.8.1
https://www.drupal.org/sa-core-2019-009
https://www.drupal.org/sa-core-2019-010
https://www.drupal.org/sa-core-2019-011
https://www.drupal.org/sa-core-2019-012
|
89ca6f7d-4f00-11e8-9b1d-00e04c1ea73d | drupal -- Drupal Core - Multiple Vulnerabilities
Drupal Security Team reports:
A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x.
This potentially allows attackers to exploit multiple attack vectors on a Drupal site,
which could result in the site being compromised. This vulnerability is related to
Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002.
Both SA-CORE-2018-002 and this vulnerability are being exploited in the wild.
Discovery 2018-04-25 Entry 2018-05-03 drupal7
< 7.58
drupal8
< 8.5.2
https://www.drupal.org/SA-CORE-2018-004
|
9b8a52fc-89c1-11e9-9ba0-4c72b94353b5 | drupal -- Drupal core - Moderately critical
Drupal Security Team reports:
CVE-2019-11831: By-passing protection of Phar Stream Wrapper Interceptor.
In order to intercept file invocations like file_exists or stat on compromised Phar archives
the base name has to be determined and checked before allowing to be handled by PHP
Phar stream handling.
The current implementation is vulnerable to path traversal leading to scenarios where the
Phar archive to be assessed is not the actual (compromised) file.
Discovery 2019-05-08 Entry 2019-06-08 drupal7
< 7.67
drupal8
< 8.7.1
https://www.drupal.org/SA-CORE-2019-007
|
4fc2df49-6279-11e7-be0f-6cf0497db129 | drupal -- Drupal Core - Multiple Vulnerabilities
Drupal Security Team Reports:
CVE-2017-6920: PECL YAML parser unsafe object handling.
CVE-2017-6921: File REST resource does not properly validate
CVE-2017-6922: Files uploaded by anonymous users into a private
file system can be accessed by other anonymous users.
Discovery 2017-06-21 Entry 2017-07-06 drupal7
< 7.56
drupal8
< 8.3.4
CVE-2017-6920
CVE-2017-6921
CVE-2017-6922
|